# MEMORANDUM **To:** File — Meridian Alloy Works **Re:** Procedural challenge to North Coast Environmental Directorate emissions-reporting rule **Framing note:** Every argument below rests on the Directorate's notice, comment record, stated basis, and reliance materials. We do not argue that the rule is unwise, that its costs exceed its benefits, or that climate reporting is unnecessary. The Directorate's assertion that "environmental benefits justify the final requirements" is not responsive to a procedural challenge and, under Rule 9, cannot be used to cure a defective record. --- ## 1. Notice for the 25,000-ton threshold — strong challenge **The defect.** The published notice proposed coverage at 100,000 tons and asked only whether the threshold should be "modestly adjusted." The final rule set the threshold at 25,000 tons — a 75% reduction that quadruples the reach of the rule downward and sweeps in a class of facilities the proposal affirmatively signaled would remain outside it. **Why "modest adjustment" does not supply notice.** The Directorate will argue that Rule 1 requires only notice of the "subjects and issues under consideration," and that the threshold was expressly under consideration. That argument fails on the words the agency chose. "Modestly adjusted" is *limiting* language. It told the regulated community that the 100,000-ton line would move at the margins, not that the entire covered universe would be redefined. Under Rule 2, the question is whether affected persons "should reasonably have anticipated the final approach." A facility at 62,000 tons — 38% below the proposed floor and far below any plausible "modest" adjustment of it — had no reason to anticipate coverage, and therefore no reason to develop and submit the cost, feasibility, and lead-time record that a covered entity would submit. **Rule 3 applies directly.** The proposal gave no notice of the *compliance burden* that became central to the final rule as applied to mid-sized emitters. Meridian's position is the cleanest possible illustration: it was a non-covered commenter on a proposal that did not reach it, and it emerged from the process as a covered entity facing a $2.4 million capital commitment. **Note on the comment period.** The Directorate gave 60 days, exceeding the 30-day minimum in Rule 1. We should concede this openly. Our claim is not that comment was too short; it is that the comment that occurred was directed at a different rule. --- ## 2. Monthly reporting — weak on logical outgrowth, strong on response and prejudice **Candid assessment.** This is our weakest logical-outgrowth claim and we should not lead with it. The notice expressly asked "whether quarterly reporting was adequate." A move to monthly reporting is the natural answer to that question if the agency concludes quarterly is *not* adequate, and Rule 2 would likely be satisfied as to reporting frequency standing alone. Worse for us, Meridian *actually commented* on monthly measurement, which the Directorate will cite as proof that the issue was reasonably anticipated. Pressing an aggressive notice theory here would invite the court to discount our stronger claims. **Better framing — three points.** *(a) The frequency question was noticed; the frequency-plus-coverage combination was not.* Meridian's exposure to monthly reporting exists only because the threshold dropped to 25,000 tons. Vacating the threshold for want of notice (Part 1) removes Meridian's monthly-reporting obligation without any need to hold that monthly reporting was itself unnoticed. This is the efficient path. *(b) Prejudice is real notwithstanding Meridian's comment.* Meridian commented as an *uncovered* observer. It flagged a feasibility concern; it had no occasion or incentive to build the record a covered entity builds — instrumentation specifications, vendor lead times, calibration and quality-assurance data, phase-in and transition alternatives, or a demonstration that monthly data would not improve data quality for facilities in the 25,000–100,000 ton band. Rule 7's harmless-error test asks whether the challenger had a meaningful opportunity to present "the substance of the omitted comment." A one-paragraph warning from a non-covered party is not the substance of the covered-entity submission the defect suppressed. *(c) The unanswered comment converts the frequency provision into an independent Rule 5 violation.* See Part 5. --- ## 3. Supplier and contractor reporting — strongest challenge This provision fails Rule 3 on every listed element: | Rule 3 element | Proposal | Final rule | |---|---|---| | Regulated conduct | facility's "own direct emissions" | calculation of third-party supplier and onsite-contractor emissions | | Data source | facility's own measurements | designated suppliers, contractors, purchased-materials records | | Compliance burden | self-reporting | obtaining, auditing, and vouching for data the facility does not generate and may lack contractual power to compel | The facts state that the notice "did not mention contractors, suppliers, purchased materials." No commenter — covered or not — could have anticipated that the rule would extend to emissions the facility neither produces nor controls. This is not a variation in degree on a noticed subject; it is a different regulatory object. There is no plausible logical-outgrowth defense, and the Directorate's own statement of basis confirms the point by tracing this requirement entirely to a document created *after* comment closed. This should be the lead claim in the petition. --- ## 4. The undisclosed post-comment model — mandatory reopening under Rule 4 **Every predicate of Rule 4 is admitted on the face of the record.** 1. *Post-comment creation:* the model was commissioned after the comment period closed. 2. *Non-disclosure:* it was never placed in the public docket, so no commenter could have addressed it by any means. 3. *Material reliance:* the final statement "cites the post-comment supply-chain model as the reason for contractor and supplier reporting." The agency has itself characterized the model as the reason for the requirement. 4. *Essential factual basis:* the model's conclusion — that facilities above 25,000 tons "often cause much larger upstream emissions" — is the sole articulated factual support both for the supply-chain provisions *and* for the numerical selection of 25,000 tons. The coincidence of the model's threshold and the rule's threshold is powerful evidence that the model, not the comment record, drove the final line. 5. *No meaningful opportunity to address:* an unpublished model cannot be contested. Commenters could not test its assumptions, emission factors, allocation methodology, data vintage, or its extrapolation from unspecified facilities to Meridian's operations. **Consequence.** Reopening was mandatory. Because the model supplies the essential factual basis for two of the three challenged provisions, its concealment independently invalidates both — the threshold as well as the supply-chain requirements. Under Rule 9, the court reviews "materials actually relied on" and will not accept a later-supplied rationale; the Directorate cannot now defend the threshold on grounds absent from the record, nor can it cure the defect by docketing the model in litigation. **Immediate practical step.** Serve a demand for the complete administrative record, including the model, its inputs, the commissioning instructions, and all internal communications concerning it. If the Directorate resists, that resistance itself supports a stay: the court cannot conduct Rule 9 review of materials the agency withholds. --- ## 5. Response to Meridian's significant comment — Rule 5 violation Meridian warned that monthly measurement would require new instrumentation. That comment "seriously challenge[s] [the agency's] factual premise" within Rule 5: the Directorate justified monthly reporting on *data quality*, and Meridian's comment asserts that monthly data cannot be produced at all without new equipment — i.e., that the premised quality gain is unattainable on the rule's own terms and timetable. The comment is concrete, on-point, and from a party the final rule covers. The final statement says only that "monthly reporting is needed for data quality." That is a restatement of the conclusion, not a response to the challenge. It does not accept, reject, qualify, or engage the instrumentation premise. Rule 5 does not require the agency to answer every point, but it does require it to address this one. The omission is squarely conceded by the facts ("does not answer Meridian's instrumentation comment"). This claim has independent value: it defeats the Directorate's best harmless-error argument. The agency cannot simultaneously say "you commented, so you were not prejudiced" and "we did not answer your comment." Where the record shows the comment was submitted and ignored, the challenger has shown at minimum *possible* prejudice — the outcome might have differed had the agency confronted the feasibility premise. --- ## 6. Good cause for immediate effectiveness — fails Rule 6 Rule 6 permits omission or shortening only where ordinary procedure is impracticable, unnecessary, or contrary to the public interest, supported by "specific contemporaneous reasons," and expressly excludes "administrative delay or a general desire for speed." - The stated reason — "climate reporting is urgent" — is a general desire for speed. It is a statement about the subject matter of the rule, not about why *this* rule could not take effect on ordinary delayed terms. - No triggering event is identified. The facts state the Directorate "gives no event that made ordinary delayed effectiveness impracticable." - The agency's own timeline refutes urgency: drafting began eighteen months before publication. An agency that took a year and a half to write a rule cannot claim that a normal effectiveness period is impracticable. That is the paradigm of administrative delay under Rule 6. - The invocation is generic rather than specific and contemporaneous. The good-cause finding should be set aside on its own, and this is the discrete issue most likely to yield fast interim relief, because it can be resolved on the four corners of the statement without any record development. --- ## 7. Harmless-error arguments — anticipated and answered Rule 7 makes harmlessness a **conjunctive** test: the error is harmless only if the challenger (i) had a meaningful opportunity to present the substance of the omitted comment **and** (ii) cannot show *possible* prejudice. The agency must win both prongs; we need win only one, and we win both on most provisions. **The Directorate will argue:** *"The notice flagged the threshold, so Meridian could have commented."* — The notice flagged a *modest* adjustment. Meridian, below the proposed floor, was told in substance that it was not a target. Rule 3 exists precisely for the case where the proposal gave no notice of the compliance burden that became central. *"Meridian commented on monthly measurement, proving opportunity."* — Only prong (i), and only partially. Meridian could not present the covered-entity substance described in Part 2(b). And prong (ii) is independently fatal: prejudice is possible and, here, demonstrable — a $2.4 million contract that must be signed within 25 days. *"Supply-chain reporting is a detail of the same reporting scheme."* — There is no opportunity argument available at all. No commenter saw the model or the subject. Prong (i) fails outright. *"The requirements are environmentally beneficial."* — Not a harmless-error argument. Rule 7 is about opportunity and prejudice, not merits; Rule 9 forbids sustaining the rule on post hoc policy justification. **Structural point.** Where the essential factual basis for a requirement was created after comment and never disclosed (Rule 4), harmlessness is effectively unavailable: it is impossible to say a party had a meaningful opportunity to address a document it never saw, and the prejudice inquiry cannot be conducted because the court itself cannot know what informed comment would have produced. --- ## 8. Standing, deadline, and remedies **Standing.** Satisfied under Rule 8. Meridian is now a covered facility (62,000 > 25,000) facing imminent compliance costs — a $2.4 million monitoring-system contract that must be executed within 25 days to meet the first reporting date. This is not speculative future injury; the expenditure is compelled by the rule's own schedule. **Deadline.** 30 days from publication. The rule was published yesterday, so we are on day 1. **File immediately — within the next 3–5 business days — not on day 29.** Two reasons: (a) the operative commercial deadline is 25 days, so a petition filed near the end of the window would leave no time for a stay ruling before Meridian must either sign the contract or risk non-compliance; (b) there is no tolling mechanism available. **Interim relief — stay.** Move for a stay of effectiveness concurrently with the petition, on an expedited schedule tied to the 25-day contract date. The strongest stay showing combines: (i) a facially invalid good-cause finding contradicted by the agency's own 18-month timeline (Part 6); (ii) an irreversible, quantified expenditure; and (iii) the fact that the material driving the rule is not in the record, so the agency cannot yet defend it under Rule 9. **Vacatur.** Seek vacatur of the three provisions that reach Meridian: - the 25,000-ton threshold (no notice; and factually grounded only in the undisclosed model); - the supplier/contractor requirement (no notice of conduct, data source, or burden; grounded solely in the undisclosed model); - the monthly-reporting requirement as applied to newly covered facilities (unanswered significant comment; and derivative of the invalid threshold). **Remand and temporary continuation — a deliberate concession.** Rule 8 lets the court continue a rule temporarily where disruption would be serious. We should *not* oppose continuation of the provisions that were properly noticed: quarterly reporting by facilities above 100,000 tons. That regime went through valid notice and 60 days of comment, and Meridian at 62,000 tons is unaffected by it. Offering this severance materially improves our position: it shows the court a clean, narrow remedy; it neutralizes any disruption argument (no one can claim reliance on requirements that took effect yesterday and rest on a document never disclosed); and it makes plain that our objection is to *process*, not to emissions reporting. The proper disposition is therefore: **stay the challenged provisions now; vacate the supply-chain requirement and the 25,000-ton threshold; remand for renewed notice and comment with the supply-chain model docketed; and set aside the good-cause finding so that any surviving requirements take effect only after ordinary delayed effectiveness.** --- ## 9. The petition to file **Petition for review and emergency motion to stay**, pleading five procedural counts in this order: 1. **Failure to disclose and reopen (Rule 4).** The supply-chain model, created after comment closed and never docketed, is the essential and admitted factual basis for the supplier/contractor requirement and for the 25,000-ton threshold. Reopening was mandatory. Lead with this count: the predicates are admitted, it reaches two provisions at once, and Rule 9 bars any post hoc repair. 2. **Supplier and contractor reporting is not a logical outgrowth (Rules 2–3).** The notice mentioned no contractors, suppliers, or purchased materials; the final rule regulates new conduct, a new data source, and a new burden. 3. **The 25,000-ton threshold is not a logical outgrowth (Rules 1–3).** A request to consider a "modest adjustment" of a 100,000-ton threshold gave no notice of a 75% reduction that sweeps in facilities the proposal placed outside its scope. 4. **Failure to respond to a significant comment (Rule 5).** The statement of basis never addresses Meridian's instrumentation comment, which directly challenges the factual premise (data quality) on which monthly reporting rests. 5. **Invalid good cause for immediate effectiveness (Rule 6).** Generalized urgency, unsupported by any specific contemporaneous event and contradicted by an 18-month drafting period, is administrative delay and a general desire for speed. **Relief requested:** stay pending review; vacatur of counts 1–3 provisions and of the monthly-reporting requirement as applied to newly covered facilities; remand with instructions to docket the model and reopen comment; and setting aside of the good-cause finding — with no objection to temporary continuation of the properly noticed 100,000-ton quarterly regime. **Discipline to maintain throughout.** The petition should nowhere assert that the rule is too expensive, that supply-chain accounting is bad policy, or that climate reporting is unimportant. The $2.4 million figure appears only twice and only for procedural purposes: to establish imminent injury for standing and to show possible prejudice under Rule 7. Framed this way, the Directorate's environmental-benefit defense is not merely unpersuasive — it is off the question the court is asked to decide.