# DMCA §1201 — 2027 Cycle Multi-Class Petition Plan

**Date:** 2026-05-23
**Cycle:** 10th triennial (NPRM mid-2026, Final Rule ~Oct 2027)
**Goal:** five new-class filings + renewals of all 2024 grants, with the long-term objective of §1201 repair exemptions covering every product category.
**Status:** planning document — needs coalition-lead sign-off per filing before evidence work begins.

This plan was developed in conversation with the §1201 archive (`analysis/lineages.json`, the nine Final Rules, and the Registers' Recommendations under `1201/`). It is not legal advice; the codified text in each Final Rule is the operative regulation.

---

## Executive summary

We file **five new-class petitions** plus **streamlined renewals** of every 2024-granted class. Each new-class filing is structured around a coherent user community + a concrete adverse-effects story, modeled on the closest existing class. Realistic outcome on the new asks: **2–4 grants, 1–3 narrowed grants, 1–2 record-builders for 2030**.

The 2024 Register denied "commercial and industrial equipment" broadly (Class 5 broader scope) and in 2021 (Class 12) for the same reason: insufficient record + non-cohesive class. Our work-around: **(a) split that bucket into cohesive user communities**, **(b) develop the record before filing, not after**, and **(c) frame each filing so the need is broad, the harm is narrow, and the additional scope does not expand copyright risk**. The Office's grants in 2024 (food-prep, medical-device, vehicle/vessel data) all turned on having concrete, named, documented use cases combined with a tight copyright posture. We need the equivalent in every filing.

**Filing structure after restructuring:**

| # | Filing | Frame |
|---|---|---|
| 1 | Agricultural & Construction Equipment | Stationary ag (gap in (b)(13)) + mobile-construction clarification |
| 2 | Scientific & Laboratory Equipment | Closes the deliberate 2024 carve-out (no prior denial, no organized opposition); direct (b)(17) medical-device analog |
| 3 | American Re-industrialization: Manufacturing Equipment | Reshoring / factory-operator autonomy; 4 sub-asks |
| 4 | General-Purpose Computing & Networking | Closes the (b)(15) consumer-gate gap for commercial-use PCs / Macs / workstations; folds in enterprise IT |
| 5 | Commercial Premises Equipment | One broad class covering software-enabled commercial-property equipment (HVAC, BMS, solar/battery/EV, commercial laundry, etc.); diversity of examples = record depth, not separate asks |

---

## The Office's own position on repair

The Register has **already endorsed** the substance of what we're petitioning for. Two of the Register's standalone policy studies, both delivered to Senators Grassley and Leahy in 2016-17, give us direct citations that pre-rebut the most common opposition arguments. (Both reports are archived under `1201/Policy Studies/`; full citation analysis in `1201/Claude Reports/2026-05-24__Office-Policy-Reports-and-2027-Plan-Implications.md`.)

**1. The Register supports a permanent repair exemption.** From the 2017 §1201 Study at PDF p. 90: *"a limited and properly‐tailored permanent exemption for [diagnosis, repair, and maintenance], including circumventing obsolete access controls for continued functioning of a device, would be consistent with the statute's overall policy goals."* The Office characterized the rulemaking as a *"somewhat ill‐fitting regulatory approach"* (p. 92, quoting former Register Peters) for cross-cutting repair issues. Our triennial filings are interim relief while Congress catches up to the Office's own recommendation.

**2. The Office expressly recommends *against* device-specific limitations.** From the 2017 §1201 Study at p. 94: *"the Office recommends against limiting an exemption to specific technologies or devices, such as motor vehicles, as any statutory language would likely be soon outpaced by technology."* Cite this whenever opposition argues that a class is "too broad." The Office's own position is that broader, device-agnostic protection is preferable.

**3. Safety concerns belong outside copyright law.** From the 2017 §1201 Study at p. 94: *"to the extent that commenters oppose an exemption for repair out of non‐copyright related concerns, such as public safety, the Office believes these matters are better addressed through laws or regulations outside of the Copyright Act."* This is the Office's own framing for our Filing 5 carve-outs (life-safety, UL 1741, IEEE 1547, EPA/DOE efficiency parameters).

**4. §117(d) is the Register's preferred statutory anchor.** The Office recommended that any repair exemption use 17 U.S.C. §117(d)'s definitions: *"the 'maintenance' of a machine is the servicing of the machine in order to make it work in accordance with its original specifications"* and *"the 'repair' of a machine is the restoring of the machine to the state of working in accordance with its original specifications."* (2017 §1201 Study at p. 94). Our class-language drafts should mirror this. The "original specifications" framing also pre-rebuts the modification / tinkering objection: we are not asking to enhance or customize devices, only restore them.

**5. The 2016 Software Study found §117(a) covers most repair as a matter of underlying copyright.** From the 2016 Study at p. 35: §117 *"should adequately protect most repair and maintenance activities."* And at p. 40: *"repair supports — rather than displaces — the purpose of the embedded programs that control that device."* For devices where the embedded software is "invisible to the consumer" (mechanical controllers, parts-pairing chips, peripheral firmware), the device buyer is the §117 owner — the underlying copyright concern dissolves. This is the doctrinal foundation for our Filings 1–3 and 5; Filing 4 needs to be more careful because the OS is "a more significant element of the transaction" (2016 Study at p. 35–36).

**6. Even the opposition has conceded repair is distinguishable.** The joint copyright-industry coalition (AAP, ESA, MPAA & RIAA) conceded in the 2016 record that *"automobile repair or other forms of repair might present a unique and distinguishable set of circumstances"* (2017 §1201 Study at p. 93 n.508). Use this when the same coalition opposes our filings in 2027.

**What's NOT in our favor:**

- The Office *rejected* a §1201(a) infringement-nexus requirement (2017 Study pp. 42–46). Reason: it would weaken copyright owners' control over online access to creative works. Our argument cannot be "TPMs on repair targets categorically lack copyright nexus."
- The Office *rejected* categorical exclusion of "device- or machine-enabling computer programs" (p. 47). Reason: line-drawing problems (video-game-console authentication, etc.). Our argument cannot be "device-control firmware is categorically outside §1201(a)."

Both rejections mean we still need the rulemaking. But neither undermines our core framing — which is that the underlying activity is non-infringing under §117 and that the Office's own permanent-exemption recommendation supports broad, device-agnostic repair relief through the rulemaking until Congress acts.

---

## Cycle calendar (anchored to the last four cycles' pattern)

| Date | Event | Our action |
|---|---|---|
| ~Jun–Jul 2026 | NPRM published | Stop scope changes; freeze filing list |
| ~Aug–Sep 2026 | Petitions due (~30–60 days post-NPRM) | File all 5 new-class petitions + renewal petitions |
| ~Dec 2026 | Round 1 (initial) comments due | **The deadline that matters** — full evidence record for each class |
| ~Mar 2027 | Round 2 (opposition) comments due | Triage which classes face opposition |
| ~Jun 2027 | Round 3 (reply) comments due | Reply on contested classes only |
| Summer 2027 | Public hearings (if Office calls them) | Witness prep for top 2–3 classes |
| ~Oct 2027 | Final Rule | Accept; use denials as 2030 record |

The hard deadline is **Round 1 (~Dec 2026)** — that's where the substantive evidence record is built. The petition itself is short. Plan the next 6 months around Round 1, not the petition.

---

## Filing 1 — Agricultural & Construction Equipment

### Scope
- **Stationary agricultural equipment** not constituting a motorized land vehicle: irrigation controllers; grain dryers and conditioning systems; milking robots and dairy automation; barn / livestock-feeding / ventilation automation; precision-ag base stations and field sensors; automated-greenhouse controllers; seed-conditioning equipment.
- **Stationary construction processing**: asphalt batch plants, concrete batch plants, aggregate processing, fixed crushing/screening.
- **Mobile construction equipment** — included as a clarifying ask: confirm that "motorized land vehicle" in (b)(13) reaches excavators, loaders, dozers, cranes-on-tracks, mobile pavers. Not a new class; a clarification on the record so OEMs stop reading the class narrowly.

### User community & political constituency
- Farmers, agricultural operators, ranchers, dairy operators.
- Construction-equipment owners (contractors, AGC members), independent service shops, equipment dealers (AED).
- Strong existing right-to-repair coalition; AFBF (Farm Bureau) and Repair Association already aligned.
- Bipartisan political surface (rural/red and right-to-repair/blue).

### Closest precedent
- 2024 §201.40(b)(13) motorized-land-vehicle class — established repair-class pattern; we are extending its logic to (a) stationary ag (gap) and (b) clarifying its reach to construction.
- 2024 §201.40(b)(14) vehicle/vessel data — useful for the data-access analog if needed.

### Draft class language (for refinement by counsel)
> Computer programs that are contained in and control the functioning of a lawfully acquired (i) agricultural machine or system that is not a motorized land vehicle, or (ii) stationary construction processing system, when circumvention is a necessary step to allow the diagnosis, maintenance, or repair of such a machine or system, and is not accomplished for the purpose of gaining access to other copyrighted works. For purposes of this paragraph, (i) the "maintenance" of a machine or system is the servicing of the machine or system in order to make it work in accordance with its original specifications and any changes to those specifications authorized for that machine or system; and (ii) the "repair" of a machine or system is the restoring of the machine or system to the state of working in accordance with its original specifications and any changes to those specifications authorized for that machine or system. (These definitions mirror those codified at (b)(15), (b)(16), and (b)(17) — (b)(13) uses different vocabulary ("diagnosis, repair, or lawful modification") and does not itself define "maintenance" or "repair.")

### Evidence requirements
- 8+ named specific instances of TPM-induced repair failure (irrigation controller bricked at season; milking robot off-line; grain dryer locked during harvest; concrete-plant controller field replacement blocked).
- Economic harm quantified — downtime cost per day during planting/harvest/calving window; opportunity cost.
- OEM service unavailability or insufficiency — rural service-call delay statistics, parts-availability gaps.
- Non-circumventing alternatives — demonstrate none exist (or are inadequate).

### Witnesses & coalition leads
- **Primary coalition lead:** Repair Association.
- **Co-leads:** AFBF, AED (construction).
- **Witnesses:** 3+ farmers, 1+ dairy operator, 1+ construction-equipment owner, 1+ independent ag mechanic, 1+ aftermarket parts supplier.
- **Allied amici:** Public Knowledge, EFF, iFixit.

### Risk assessment
- **Low.** Strongest filing on the list. Stationary-ag is a clean gap in the existing vehicle class; the construction clarification is the Office's preferred posture (clarify rather than re-codify). Risk is being too greedy and including industrial-scale ag (mining-scale processing) that overlaps Filing 3.

### Expected outcome
- New (b)(N) class covering stationary ag + stationary construction processing.
- On-record clarification that (b)(13) reaches mobile construction.
- **Confidence: high.**

---

## Filing 2 — Scientific & Laboratory Equipment

> **Repair of software-enabled scientific and laboratory instruments — the cleanest filing in the 2027 portfolio.** The 2024 Class 5 proponents (Public Knowledge & iFixit, Initial Comment at PDF p. 9) explicitly excluded *"devices designed or marketed for medical, scientific, or consumer use"* from their petition. Scientific/lab is a **deliberate carve-out, not a denial** — the §1201 record is clean and unopposed. This filing closes that gap with a comprehensive record across the full surface of research instrumentation.

### Why now
- **The 2024 deliberate carve-out** — the Office has never said "no" to a scientific-instrument repair class because no one has ever asked. Already shown as a gap row in the repair diagram.
- **The 2017 §1201 Study** formally recommended Congress adopt a permanent statutory repair exemption (PDF pp. 88–96). The Office's own analytical position supports the filing.
- **The user community is unusually well-organized** for record-building: research universities, biotech, pharma, and ISOs are all heavily reliant on instruments they can't repair when OEM service is unavailable, expensive, or abandoned.

### Example instruments (record depth — not separate asks)
- Mass spectrometers and analytical chains (HPLC, UPLC, GC, GC-MS, LC-MS).
- Genomic / proteomic sequencers (Illumina, PacBio, Oxford Nanopore platforms).
- Electron microscopes (TEM, SEM, FIB, cryo-EM); confocal and super-resolution optical microscopes.
- Flow cytometers and cell sorters.
- Spectrophotometers (UV-Vis, FTIR, NMR), thermal cyclers / qPCR machines, ultracentrifuges, plate readers.
- Calibration, metrology, and electronic test & measurement equipment.

These are *examples* that build the per-category record. The class itself is scientific and laboratory equipment broadly. Naming specific instrument types is record depth, not a list of separate asks — and demonstrates that the same TPM-lockout pattern recurs across the full surface of research instrumentation.

### Copyright posture
The TPMs at issue (service-mode passwords, OEM calibration software, authenticated parts, encrypted firmware, phone-home license checks) gate the instrument's device-control firmware — they do not gate access to copyrighted creative works. Per the 2016 Software Study at p. 40, *"repair supports — rather than displaces — the purpose of the embedded programs that control that device"* — and §117(a) *"should adequately protect most repair and maintenance activities"* (2016 Study at p. 35). The 2017 §1201 Study went further and recommended Congress adopt a permanent statutory repair exemption keyed to §117(d)'s "maintenance" and "repair" definitions. Even the opposition coalition conceded that repair *"might present a unique and distinguishable set of circumstances"* (AAP, ESA, MPAA & RIAA, 2016 record, cited at 2017 Study p. 93 n.508) — scientific instruments fit that distinguishable-set framing exactly.

### User community
Research universities and core facilities, biotech and pharma R&D, contract research organizations, independent service organizations (ISOs) serving instrument repair, federally-funded research institutions. The user is institutional and budget-constrained — most lab managers depend on ISOs because OEM service contracts are 15–25% of instrument capex per year.

### Closest precedent
- 2024 §201.40(b)(17) medical-device repair — closest pattern: same ISO-repair industry structure, same "related data files" issue (calibration files, run-method files), same professional/institutional user posture.
- 2024 §201.40(b)(16) retail commercial food-prep — analogous "institutional commercial user" template (and direct evidence that the Office grants when the record is concrete).

### Draft class language
> Computer programs that are contained in and control the functioning of a lawfully acquired scientific, laboratory, or research instrument, and related data files (including instrument calibration files, analytical method files, and run logs), when circumvention is a necessary step to allow the diagnosis, maintenance, or repair of such instrument, and is not accomplished for the purpose of gaining access to other copyrighted works. For purposes of this paragraph, (i) the "maintenance" of an instrument is the servicing of the instrument in order to make it work in accordance with its original specifications and any changes to those specifications authorized for that instrument; and (ii) the "repair" of an instrument is the restoring of the instrument to the state of working in accordance with its original specifications and any changes to those specifications authorized for that instrument. (Definitions mirror those codified at (b)(15)–(b)(17).)

### Record-building plan
- Service-contract cost differentials between OEM and independent ISOs (commonly 2–3× for the same scope of work).
- Documented refusal-to-service by OEMs after end-of-life on instruments still in research use.
- Downtime-cost impact on grant-funded research — NIH / NSF / DOE cycle delays, missed publication deadlines, lost graduate-student productivity.
- Core-facility utilization records from research universities showing instrument-availability shortfalls.
- OEM parts-availability gaps for instruments more than ~7 years old.
- "Phone-home" authentication that bricks instruments without a manufacturer license check (specific named instrument lines with this behavior).

### Witnesses & coalition leads
- **Primary coalition lead:** Public Knowledge + Repair Association.
- **Co-leads:** University procurement consortia (APLU / AAU member institutions); scientific-instrument ISO industry trade groups; research-society instrumentation interests (ACS analytical division; ASMS for mass-spec; ASCB / similar for microscopy); SERI (sustainability — abandoned-instrument e-waste).
- **Witnesses:** 2+ university core-facility directors (mass-spec, sequencing, and EM cores at separate institutions); 1+ biotech or pharma lab manager; 1+ scientific-instrument ISO repair company; 1+ NIH- or NSF-funded PI documenting research delay from equipment lockouts.
- **Allied amici:** university research-VP offices.

### Risk assessment
- **Low.** Direct analog of the 2024 medical-device grant. Clean §1201 record (no prior denial); no organized opposition (the deliberate 2024 carve-out means the usual rightsholder coalition has not staked out a position on lab equipment specifically). The strategic variable, as in every filing, is record depth — and the user community is unusually well-organized for record-building.

### Expected outcome
- New (b)(N) for scientific and laboratory equipment repair, with related-data-files coverage (calibration files, run-method files) on the (b)(17) model.
- **Confidence: very high.**

---

## Filing 3 — American Re-industrialization: Manufacturing Equipment

> Anchored to the post-CHIPS-Act political moment: **domestic factory owners need autonomy over their own operations to ramp up American manufacturing.** Covers the full envelope of equipment a U.S. factory needs to operate — production lines, factory-floor automation, fab tooling, and manufacturing-facility infrastructure. Same substantive ask as the post-2024 industrial-automation strategy, *reframed around reshoring and operator sovereignty* and selectively expanded into adjacent fab/facility infrastructure.

### Political frame
- Reshoring, domestic manufacturing autonomy, and factory-operator sovereignty over their own equipment.
- Anchors to the CHIPS Act, the IRA's domestic-content provisions, and the bipartisan re-industrialization consensus.
- Reframes a twice-denied "industrial repair" ask into an "American competitiveness" ask — without changing the underlying copyright posture.
- Strategically: the reshoring framing may split NAM internally (large multinational OEMs vs. domestic mid-sized manufacturers who are NAM's growing constituency).

### Scope — 4 sub-asks
Filed as one petition (preferred) or four depending on Office preference:

- **3a · Regulated production lines.** PLCs and process controllers governing food / beverage / pharma manufacturing subject to FDA / FSMA documentation requirements. Strongest harm story: recall-traceability and audit requirements compound the lock-in cost.
- **3b · Abandoned-vendor / end-of-life industrial controllers.** Explicit class for equipment whose OEM no longer supports the product. Strongest copyright posture — vendor has exited the market, so there is no rights-holder to harm.
- **3c · Factory-floor automation.** Mid-sized factory robotics and motion controllers (assembly-line, palletizing, machine tending); industrial 3D printers (Stratasys, EOS, Markforged, HP); semiconductor-fab process tools; industrial test & measurement equipment used for production QA.
- **3d · Manufacturing facility infrastructure.** Industrial-scale HVAC for factory production environments, cleanroom HVAC and control systems, factory-scale power management. *Distinguished from Filing 5's commercial HVAC by user (factory operator vs. building owner) and purpose (production-environment process control vs. occupant comfort).*

### User community
- U.S. mid-sized manufacturers, in-house maintenance teams, third-party industrial service technicians.
- Reshoring beneficiaries: CHIPS-Act-funded semiconductor fabs, IRA-eligible clean-energy manufacturers, pharmaceutical-onshoring operators.
- Distinct from Filing 2 (small service-business + research labs), Filing 4 (general computing / enterprise IT), and Filing 5 (commercial buildings).

### Closest precedent
- 2024 §201.40(b)(17) medical devices — closest in the "professional/institutional repair under firmware control" pattern.
- 2024 §201.40(b)(21) 3D-printer feedstock — adjacent (does not reach device repair).
- **Adverse precedent:** 2021 Class 12 and 2024 Class 5 (broader scope) denials. The re-industrialization framing is the strategic response to those denials.

### Draft class language (4 paragraphs)
> (i) Computer programs that are contained in and control the functioning of programmable logic controllers operating commercial packaging, filling, or process equipment subject to recordkeeping requirements under the Food, Drug, and Cosmetic Act or the Food Safety Modernization Act, when circumvention is a necessary step to allow the diagnosis, maintenance, or repair of such equipment.
>
> (ii) Computer programs that are contained in and control the functioning of any lawfully acquired industrial control system or automation equipment for which the manufacturer has discontinued support and replacement parts are not commercially available, when circumvention is a necessary step to allow the diagnosis, maintenance, or repair of such equipment.
>
> (iii) Computer programs that are contained in and control the functioning of a lawfully acquired industrial 3D printer, factory robot, motion controller, semiconductor-fabrication process tool, or production test and measurement instrument, when circumvention is a necessary step to allow the diagnosis, maintenance, or repair of such equipment.
>
> (iv) Computer programs that are contained in and control the functioning of an industrial-scale heating, ventilation, air-conditioning, cleanroom, or facility-power-management system that is used to maintain the production environment of a manufacturing facility, when circumvention is a necessary step to allow the diagnosis, maintenance, or repair of such a system.

### Evidence requirements
- For 3a (regulated production): named pharma / food-processor case studies; FDA-traceability impact analysis; reasons existing vendor-only service is inadequate.
- For 3b (abandoned vendors): catalog of significantly-installed industrial automation product lines whose OEM has discontinued support; documented orphan-equipment population.
- For 3c (factory floor): mid-size manufacturer testimony; refusal-to-service data; ROI of repair vs. replacement; AMUG-collected service-failure stories for 3D printers; semiconductor-fab tool downtime impact on CHIPS-Act-funded fab ramp-up.
- For 3d (facility infrastructure): documented industrial-HVAC lockouts in production facilities; cleanroom-system bricking incidents in biotech and semiconductor manufacturing.

### Witnesses & coalition leads
- **Primary coalition lead:** Repair Association industrial track + Reshoring Initiative.
- **Co-leads:** SMRP (Maintenance & Reliability Professionals); AMUG (additive manufacturing); manufacturing-policy think tanks aligned with the post-CHIPS-Act agenda; mid-sized manufacturer associations (SME, NTMA); semiconductor-equipment user groups for the fab-tool sub-leg.
- **Witnesses:** 2+ pharma / food-processor maintenance managers; 2+ manufacturers with orphaned automation; 1+ industrial 3D-print service bureau; 1+ university makerspace with industrial equipment; 1+ CHIPS-Act-funded fab maintenance director (or analogous reshoring manufacturer).
- **Opposition to expect:** PMMI, NAM (mixed — see political frame above), individual OEMs (Stratasys, ABB, Rockwell, Siemens-aligned voices, Applied Materials, Lam Research for fab tools).

### Risk assessment
- **Medium-high.** Office has denied this bucket twice; the re-industrialization framing is the strategic response, not a guarantee. Four sub-asks give multiple shots. **3b (abandoned vendor) remains the most likely to win** because copyright concern is weakest when the vendor has exited. **3d (facility infrastructure) is the highest-risk sub-ask** — most novel and most opposed.

### Expected outcome
- 1–2 of 4 sub-asks granted (most likely 3b abandoned-vendor and either 3a regulated-pharma or 3c factory-floor).
- Other sub-asks build the 2030 record.
- The political frame may produce sympathetic Register dicta even where the scope is denied — useful for the 2030 cycle.
- **Confidence: medium-low.**

---

## Filing 4 — General-Purpose Computing & Networking

> Hardware repair under firmware lockout across the full general-purpose computing stack — from consumer-grade laptops used commercially through professional workstations through datacenter hardware. **The (b)(15) consumer-device class's "primarily designed for use by consumers" gate is genuinely ambiguous for PCs / Macs / laptops used in commercial settings — this filing closes that gap explicitly**, and folds enterprise IT in alongside it under a unified "hardware repair, not software access" framing.

### Scope — general-purpose computing
- Consumer-grade computers in commercial use — laptops, desktops, all-in-ones used by businesses, schools, healthcare practices, government agencies, nonprofits.
- Professional workstations — Apple Mac Pro / Mac Studio, Dell Precision, HP Z-series, Lenovo ThinkStation. Clearly outside (b)(15)'s "consumer" gate by design and marketing.
- Apple Silicon parts-pairing across the Mac line — T2 / Secure Enclave authentication; locked SSDs and Touch-ID parts; soldered RAM with brick-on-replacement behavior.
- ChromeOS and Windows-Hello hardware bindings; TPM-anchored boot lockouts after motherboard replacement.

### Scope — networking & datacenter
- Servers and server boards (CPU, memory, storage, NIC replacement).
- Network switches, routers, optical/transport gear (port-level component replacement, fan/PSU swap).
- Storage arrays (SSD/HDD replacement, controller card replacement).
- UPS / PDU / datacenter power equipment (battery, board, monitoring-card replacement).
- Datacenter environmental units (CRAC/CRAH controllers, in-row cooling).

### Critical framing — narrowest scope wins
- Petition is for **hardware repair under firmware lockout** only.
- Explicitly **excludes**:
  - Bypassing software entitlements / per-port / per-VM / capacity-based licensing.
  - Modifying or accessing the OS, hypervisor, or management-plane software beyond what is strictly necessary for hardware component substitution.
  - Defeating subscription gates on software features or DRM-protected content (FairPlay, Widevine, streaming-service DRM).
- This is the lesson from 2024: broad framings on computing lose because the Office sees software-licensing or content-DRM concerns. Carving narrowly to hardware-repair-only changes the legal posture.
- **Doctrinal foundation:** the 2016 Software Study draws a distinction we explicitly track. Embedded software that is "invisible to the consumer" (mechanical controllers, peripheral firmware, parts-pairing chips, T2/Secure-Enclave authentication of hardware components) is owned by the device buyer for §117(a) purposes (2016 Study at p. 35). Software that is "a more significant element of the transaction" — the OS — is more likely treated as licensed (id.). Our scope sits squarely on the owned-firmware side of that line: we're asking to circumvent component-authentication so users can replace failed *hardware*, not to access or modify the *OS*. The exclusions above make that distinction explicit so opposition cannot conflate the two.

### User community & political constituency
- **Commercial computing leg:** businesses, schools, healthcare practices, government agencies, nonprofits using PCs / Macs / laptops / workstations; school IT directors; small-business IT operators; MSPs and managed-IT providers.
- **Enterprise IT leg:** enterprise IT operators, MSPs, hyperscaler secondary-market refurbishers, sustainability/e-waste-reduction advocates.
- Distinct user from any other filing.

### Why now
- **(b)(15) gap on commercial use:** (b)(15) reaches devices "primarily designed for use by consumers." Commercial-use PCs and workstations sit outside that gate by both design intent and marketing.
- **2012 SFLC denial is stale:** Only PC-repair petition ever filed (2012, denied for evidentiary thinness). That denial is 13 years old; the landscape has changed completely — Apple Silicon parts-pairing, locked SSDs, T2 / secure-enclave authentication, surface bonding.
- **Refurbisher data is now mature:** SERI, ITRH, e-waste-diversion impact at scale.

### Closest precedent
- 2024 §201.40(b)(15) consumer-device repair — analogous for non-commercial PCs; this filing extends the same logic to commercial use of the same hardware.
- 2024 §201.40(b)(17) medical devices — closest "professional repair under firmware control, including related data files" template for the enterprise IT leg.

### Draft class language (2 paragraphs)
> (i) Computer programs that are contained in and control the functioning of a lawfully acquired general-purpose computing device — including desktops, laptops, all-in-ones, and professional workstations — when the device is used in a commercial, educational, governmental, or nonprofit setting, and when circumvention is a necessary step to allow the diagnosis, maintenance, or repair of such a device.
>
> (ii) Computer programs that are contained in and control the functioning of a lawfully acquired enterprise computing or networking device — including servers, network switches, routers, storage arrays, uninterruptible power supplies, and datacenter environmental equipment — when circumvention is a necessary step to allow the diagnosis, maintenance, or repair of such a device.
>
> In each case: "Diagnosis, maintenance, or repair" is limited to the restoration of the device or its components to working in accordance with the device's original specifications; circumvention is not accomplished for the purpose of bypassing software licensing, entitlement, or subscription mechanisms, or for accessing operating-system, management-plane, or DRM-protected content beyond what is necessary for hardware component replacement; and any technological measures circumvented are restored to their original state to the extent reasonably practicable upon completion of the repair.

### Evidence requirements
- **Commercial-computing leg:** specific named cases of Apple Silicon parts-pairing blocking repair; documented business / school / nonprofit lockouts; documented Apple repair-program denials for commercial users; ChromeOS and Windows-Hello hardware-binding cases.
- **Enterprise leg:** refurbisher-industry data — market size, e-waste-diversion impact, specific equipment categories blocked; specific named cases (storage-array PSU swap blocked by chassis firmware; switch port-locked PSU; server board with TPM checks on component replacement); sustainability impact quantified.
- Explicit non-impact on software licensing or content DRM — show concrete examples that the petition's scope does NOT include those concerns.

### Witnesses & coalition leads
- **Primary coalition lead:** Repair Association IT / PC track + SERI (sustainability) or ITRH (IT-refurbisher industry).
- **Co-leads:** EFF; nonprofit IT-refurbisher consortia; commercial-PC user communities (school IT, small-business IT, nonprofit / philanthropy IT); MSPs and managed-IT trade associations.
- **Commercial-computing witnesses:** 2+ school IT directors; 1+ small-business IT operator; 1+ MSP serving SMB / nonprofit clients; 1+ independent Mac repair shop with commercial customers.
- **Enterprise witnesses:** 2+ enterprise refurbishers (Sims, ITRenew analogs); 1+ MSP; 1+ sustainability / circular-economy advocate; 1+ enterprise IT director willing to testify about lock-in.
- **Opposition:** Apple (most aggressive — has fought repair exemptions across multiple cycles), Microsoft, HPE, Dell, Cisco, NetApp, Lenovo. **Strongest opposition of any filing.**

### Risk assessment
- **High for full scope. Medium for a commercial-PC + workstation carve-out** (clearly outside (b)(15)'s consumer gate). The narrow framing — hardware repair only, no licensing / OS access / content-DRM bypass — is essential. Apple will fight every variant. Strategy: file knowing the full scope likely gets denied, but the carve-outs and the on-record record build the 2030 case.

### Expected outcome
- **Likely partial grant.** Strongest case: **professional workstations** (Mac Pro, Dell Precision, HP Z) — clearly commercial by design.
- Medium case: **commercial-use laptops / desktops** (Office may say (b)(15) already covers and decline to extend).
- Datacenter / enterprise gear: likely denied at full scope; narrow **abandoned-vendor IT carve-out** plausible (parallel to Filing 3b).
- **Confidence: medium-low for full grant; medium-high for workstation + carve-outs; high for record-building.**

---

## Filing 5 — Commercial Premises Equipment

> **One broad class covering software-enabled equipment installed on commercial, institutional, and multi-family premises that uses TPMs to gate physical repair.** The diversity of equipment categories below is not an argument for separate filings — it is evidence that this is a single systemic problem affecting one coherent user community (operators of commercial premises). The breadth of the class follows from the breadth of the record.

### Why one broad class

A property owner faces the *same* §1201 problem whether the locked equipment is the building's HVAC, the laundry room's washing machines, the parking lot's EV charger, the basement's solar inverter, the lobby's elevator-access controller, or the gym's connected treadmill. Same TPM patterns (service-mode passwords, parts-pairing, OEM-only software, phone-home authentication). Same harm pattern (operator can't repair what they own; OEM monopoly drives up service cost; abandoned-vendor equipment becomes unrepairable e-waste). Same copyright posture (firmware gating device function, not gating access to creative works).

Splitting the class by equipment category would mis-frame a systemic issue as a series of niche concerns. The 2017 §1201 Study itself (PDF p. 94) puts the point explicitly: the Office *"recommends against limiting an exemption to specific technologies or devices, such as motor vehicles, as any statutory language would likely be soon outpaced by technology."*

### Example equipment (record depth — not separate asks)

- **Commercial HVAC** — rooftop units, chillers, VRF systems, walk-in refrigeration, commercial-scale heating/cooling. Heavy lockouts (Carrier, Trane, Daikin, Honeywell, Johnson Controls service-tech-only software). *Excludes Filing 3's industrial-scale factory HVAC and the residential HVAC already reached by (b)(15)'s home-systems leg.*
- **Building management systems (BMS)** and building automation controllers (Niagara, Tridium, etc.).
- **Commercial elevator and access controllers** — with life-safety carve-out (see below).
- **Solar inverters and microinverter systems** — Enphase, SolarEdge, SMA, Fronius, GoodWe. Installer-only software gates everything from a fault-reset to a board replacement.
- **Commercial battery energy-storage systems** — Tesla Powerwall through Megapack-scale, LG, Enphase IQ, EG4.
- **Energy management systems (EMS) and microgrid controllers.**
- **EV charging infrastructure** — Level 2 and DC fast chargers in commercial, fleet, multi-family, and workplace settings (ChargePoint, EVgo, Blink, Tesla). Documented network-collapse bricking incidents.
- **Commercial laundry** — Alliance/Speed Queen, Continental, Dexter, Maytag Commercial; service-mode lockouts documented in laundromat and hospitality-laundry operations.
- **Commercial dishwashing equipment** (Hobart service codes) not in (b)(16)'s food-prep class — institutional kitchens, hotels, factories.
- **Commercial espresso, garment-care, minibar, and vending equipment** — brand-dependent service modes; record-depth varies but contributes to the breadth-of-pattern argument.
- **Commercial fitness and wellness equipment** — Life Fitness, Precor, Technogym, Matrix, Cybex. Diagnostic service modes; lighter parts-pairing than the heavy-lockout categories above. Included because it costs us nothing and helps establish the equipment-breadth pattern.
- **Commercial cleaning equipment** — Tennant, Nilfisk, Kärcher Pro; mostly mechanical but increasingly firmware-controlled. Same record-breadth purpose.

These are *examples*, not a menu of separate asks. Each contributes to the record showing the same TPM-gating-repair pattern across the full surface of commercial-premises equipment.

### Critical framing — safety

- Office will worry about grid-interconnection and life-safety. The class must:
  - Limit repair to restoration of original specifications.
  - Exclude any modification that changes the equipment's grid-interconnect behavior, safety setpoints, or certified parameters (UL 1741, IEEE 1547).
  - Carve out life-safety systems entirely (fire alarm, smoke control, intrusion detection, elevator interlock, sprinkler controls).
  - Carve out modifications that affect HVAC's regulated efficiency or emissions parameters (EPA, DOE).
- **The Office's own framing supports this approach.** From the 2017 §1201 Study at p. 94: *"to the extent that commenters oppose an exemption for repair out of non‐copyright related concerns, such as public safety, the Office believes these matters are better addressed through laws or regulations outside of the Copyright Act."* Our carve-outs implement that direction: safety regulation belongs to UL, IEEE, EPA, DOE, and AHJ inspection — not §1201. Cite this when opposition (Tesla, Carrier, Trane, etc.) raises safety arguments against the repair exemption.

### Unified user community

Operators of commercial-premises equipment: commercial-property owners, BOMA / IFMA members, hospital and university facilities staff, hotel and hospitality operators, laundromat and small-commercial operators, gym and fitness-center owners, energy operators, EV-charging-network operators, and the independent service organizations (ISOs) that serve all of them. The user is defined by *what they own and operate*, not by what specific equipment category we pick out. Distinct from Filing 2 (research institutions), Filing 3 (factory operators), and Filing 4 (general computing). The Office's preferred "cohesive user community" test is satisfied — the breadth comes from the equipment, not the user.

### Closest precedent

- 2024 §201.40(b)(13) vehicle/vessel — vehicles have safety-critical components and the Office accepted "restore original specifications" repair. Direct precedent for safety-bearing equipment.
- 2024 §201.40(b)(16) retail commercial food-prep — commercial-operator user community; the model for granting commercial repair.
- 2024 §201.40(b)(17) medical devices — "professional repair, related data files included" pattern.
- 2024 §201.40(b)(15) consumer-devices home-systems leg — analog for the residential side of the same equipment categories (this filing extends the same logic to the commercial side).

### Draft class language

> Computer programs that are contained in and control the functioning of a lawfully acquired equipment system installed on commercial, institutional, or multi-family premises — including, but not limited to, heating, ventilation, air-conditioning, refrigeration, building-management, building-automation, energy-generation, energy-storage, energy-management, electric-vehicle-charging, commercial-laundry, commercial-dishwashing, commercial-fitness, commercial-cleaning, and commercial-hospitality equipment — when circumvention is a necessary step to allow the diagnosis, maintenance, or repair of such equipment.
>
> This paragraph does not apply to: (i) fire, security, intrusion, or life-safety systems; (ii) industrial-scale equipment used in manufacturing (which is the subject of paragraph (b)(N+3)); or (iii) factory-floor production equipment.
>
> Such circumvention shall not modify the equipment's certified grid-interconnect behavior (UL 1741, IEEE 1547), life-safety parameters, or regulated efficiency or emissions parameters (EPA, DOE); and any technological measures circumvented are restored to their original state to the extent reasonably practicable upon completion of the repair.
>
> For purposes of this paragraph, (i) the "maintenance" of equipment is the servicing of the equipment in order to make it work in accordance with its original specifications and any changes to those specifications authorized for that equipment; and (ii) the "repair" of equipment is the restoring of the equipment to the state of working in accordance with its original specifications and any changes to those specifications authorized for that equipment.

### Record-building plan

The record-depth across categories is what wins this filing. Two-witness-per-category target:

- 2+ commercial HVAC operators / building owners with documented lockouts (Carrier, Trane, Daikin, Honeywell, Johnson Controls cases).
- 2+ BMS service technicians at non-OEM service companies.
- 2+ solar installers (SunPower-aftermath, abandoned-vendor; Enphase / SolarEdge installer-software gating).
- 2+ EV-charger operators (including fleet operator).
- 2+ commercial-laundry operators (laundromat + hospitality / healthcare laundry).
- 1+ each from commercial-dishwasher, commercial-fitness, commercial-cleaning, and commercial-hospitality (espresso, garment care, vending) categories.
- 1+ grid-safety engineer (to validate the safety carve-outs).
- 1+ ISO industry representative covering the cross-category service-monopoly pattern.

For each category: named operators, named OEMs, named lockout incidents, documented service-cost differentials between OEM and independent service, documented refusal-to-service-after-EOL incidents. The 2024 grants turned on concrete vendor-lock-in cases (the McDonald's-ice-cream pattern). Replicate per category — the breadth of evidence IS the argument for the class.

### Witnesses & coalition leads

- **Primary coalition lead:** BOMA (Building Owners and Managers Association) + SEIA (Solar Energy Industries Association).
- **Co-leads:** IFMA (International Facility Management Association); ChargePoint and fleet-operator coalitions; local-solar advocates (Solar United Neighbors); IREC (Interstate Renewable Energy Council); NFIB on the small-commercial-operator side; commercial-laundry trade associations; independent gym, hospitality, and cleaning operator associations.
- **Opposition:** Tesla (EV chargers + solar + batteries combined), Enphase, SolarEdge; Carrier, Trane, Daikin, Honeywell, Johnson Controls (commercial HVAC); Hobart (dishwashers); Alliance/Speed Queen (commercial laundry). Opposition surface is broader than narrower-class options would produce; the strategic answer is record depth, not scope reduction.

### Risk assessment

- **Medium-high.** The variable here is record depth, not class breadth. The 2017 Study's "ill-fitting rulemaking" framing and the 2017 recommendation against device-specific limitations (PDF p. 94) both support a broad class. A thin record at Round 1 — not the breadth itself — is what would lose this filing. Plan the next 8 months around evidence development across the categories above.

### Expected outcome

- Single new (b)(N) for software-enabled commercial-premises equipment, with explicit life-safety and grid-interconnect carve-outs.
- Office may codify in two paragraphs (e.g., one for HVAC/BMS/elevator-access, one for energy/EV/commercial-operator categories) — pre-position with that fallback in the petition.
- **Highest-confidence sub-categories under the unified class:** EV charging, commercial HVAC.
- **Most opposition:** solar/battery.
- **Confidence: medium-high.**

---

## Renewals (streamlined process)

Every class granted in 2024 must be renewed via the streamlined process — petition only, low-effort. **Do not forget any of these:**

| Class | Topic |
|---|---|
| (b)(1)–(b)(3) | Motion pictures — criticism/comment clips; captioning & audio description; preservation/replacement |
| (b)(4) | Motion pictures — TDM research |
| (b)(5) | Literary works (electronic) — TDM research |
| (b)(6) | Literary works + previously published musical notation — accessibility |
| (b)(7) | Medical-device data compilations — patient access |
| (b)(8) | Wireless devices — unlocking |
| (b)(9) | Smartphones & portable all-purpose mobile computing devices — jailbreaking |
| (b)(10) | Smart televisions — jailbreaking |
| (b)(11) | Voice assistant devices — jailbreaking |
| (b)(12) | Routers and dedicated network devices — jailbreaking |
| (b)(13) | Motorized land vehicles AND marine vessels — diagnosis/repair/lawful modification |
| (b)(14) | Motorized land vehicles AND marine vessels — owner access to operational/diagnostic/telematics data |
| (b)(15) | Consumer devices generally — diagnosis/maintenance/repair |
| (b)(16) | Retail-level commercial food preparation equipment — diagnosis/maintenance/repair |
| (b)(17) | Medical devices and systems — diagnosis/maintenance/repair |
| (b)(18) | Good-faith security research |
| (b)(19) | Video games — preservation when authentication server abandoned |
| (b)(20) | Software preservation by libraries/archives/museums |
| (b)(21) | 3D printers — feedstock interoperability |
| (b)(22) | FOSS computer programs — investigation of potential license infringement |

Renewal petitions are short and primarily say "no relevant change in circumstances; no marketplace alternatives have emerged; we hereby petition for renewal." Assign one person to handle all renewals as a single batch — should be ~2 days of work total.

---

## Phased action plan

### Phase 1 — Scope confirmation & coalition assembly (now → end of Q3 2026)
**Deadline: Sep 2026 (when NPRM lands).**
1. Confirm final filing scope (this document).
2. Recruit a named coalition lead per filing (5 named individuals/orgs).
3. Sign an evidence-intake commitment with each coalition.
4. Open a shared evidence-collection workspace (the rest of this plan rolls into it).

### Phase 2 — Evidence development (Q2 2026 → Q4 2026)
**Deadline: Round 1 comment date (~Dec 2026).**
1. Per-filing evidence brief: 5–10 pages each, with specific named instances, economic harm, OEM service-availability data, and absence-of-alternatives analysis.
2. Recruit witnesses (minimum 2 per filing, target 4+).
3. Get pre-commitment letters from coalition partners.
4. Begin draft Round 1 comment per filing in parallel.

### Phase 3 — Petition drafting & filing (Q3 2026, on the NPRM clock)
**Deadline: ~30–60 days after NPRM (~Aug–Sep 2026).**
1. Draft 5 petitions modeled on the closest existing class language (drafts above).
2. Coordinate with allies — multiple petitioners on each class is fine; pre-arrange a lead so the Office doesn't have to consolidate.
3. File renewal petitions as a single batch.

### Phase 4 — Round 1 comments (~Dec 2026)
**The critical deadline.** Each filing gets its long-form initial comment with the Phase 2 evidence. Each comment should:
- Lead with the concrete, named-instance harms.
- Show non-circumventing alternatives are inadequate.
- Show the proposed exemption is no broader than necessary.
- Address known opposition arguments preemptively.

### Phase 5 — Round 2 & 3 + hearings (Q1 → Q3 2027)
1. Read all Round 2 (opposition) filings; triage which classes need reply.
2. Round 3 (reply) — written response to opposition arguments. Focus on classes with substantive opposition; let uncontested ones coast.
3. Prepare for hearings (if Office calls them) — typically the Office picks the most-contested classes for hearings. Expect Filings 3, 4, and possibly 5 to be called.

### Phase 6 — Final Rule (~Oct 2027)
1. Document the outcomes per filing.
2. For denials: pull the Register's reasoning and convert into 2030-cycle TODOs (evidence gaps to fill, witnesses to add, class-language refinements).

---

## Realistic outcome distribution

Based on the 2021 / 2024 patterns:

| Filing | Likely outcome |
|---|---|
| 1. Ag & Construction | **Granted.** Possibly with separate paragraphs for ag and construction-stationary. Mobile-construction clarification recorded. |
| 2. Scientific & Laboratory Equipment | **Granted.** Cleanest filing in the portfolio — deliberate 2024 carve-out means no prior denial and no organized opposition. Direct (b)(17) medical-device analog. |
| 3. American Re-industrialization | **1–2 of 4 sub-asks granted** — most likely abandoned-vendor (3b) plus one of regulated-pharma (3a) or factory-floor (3c). Others build 2030 record. Re-industrialization framing may produce sympathetic Register dicta even where scope is denied. |
| 4. General-Purpose Computing & Networking | **Partial grant.** Strongest case: commercial workstations + PCs (outside (b)(15)'s consumer gate). Datacenter / enterprise IT denied at full scope; abandoned-vendor IT carve-out plausible. |
| 5. Commercial Premises Equipment | **Single (b)(N), likely codified in 1–2 paragraphs.** The unified user-community frame and the device-agnostic 2017 Register recommendation both support breadth. Strongest sub-categories under the unified class: commercial HVAC, EV charging. Heavier opposition on solar/battery; record depth across categories carries the filing as a whole. |

**Net new substantive grants: ~3–5 classes.** For comparison, 2024 produced 3 substantively-new grants (food-prep, vehicle/vessel data, plus expansions). This would be a notably-productive cycle.

**Long-term:** the denials are not failures — every denial's record is what enables a 2030 grant. The 2024 food-prep grant was built on the 2021 commercial/industrial denial's record. We are explicitly running the same play across 5 filings.

**The Register's permanent-exemption recommendation is the political backdrop.** The 2017 §1201 Study (PDF pp. 88–96) recommended Congress adopt a permanent statutory repair exemption keyed to §117(d). Congress has not acted in nearly a decade. That recommendation is still on the table, and every triennial repair win builds the case that the rulemaking is doing work Congress should have made permanent. Cite the Register's own recommendation whenever opposition argues a class is "too broad" or "should wait for legislation": the Office's own view is that the rulemaking is "ill-fitting" for these issues and that broader, device-agnostic protection is what the statute eventually needs. Triennial wins are the bridge to (someday) statutory relief.

---

## Deferred to the 2030 cycle

- **Professional A/V / broadcast / cinema equipment.** Distinct copyright concerns (these devices process audiovisual works); needs careful framing around device-control firmware that does NOT touch access-to-works. Should be its own filing with its own coalition (Society of Broadcast Engineers, post-production trade groups). Not included now to avoid diluting the five focused filings.

---

## Open decisions / what we need from you

1. **Coalition leads per filing.** This plan assumes Repair Association / Public Knowledge / EFF / AFBF / SEIA / SERI as primary partners. Confirm coordination with each before evidence work starts.
2. **Resourcing.** Evidence development is the long pole — 5 filings × ~6 months × dedicated researcher time. Budget for that or scope-cut to 3–4 filings.
3. **Data-layer tracking.** Recommend extending `analysis/lineages.json` with `kind: "planned"`, `target_cycle: 2027`, and per-filing `status` ("scoping" → "evidence" → "filed" → "round-1" → "decided"). The diagram could then render a 2027 forward-looking column for each planned filing.
4. **2030 priorities.** Pro A/V deferred here; should the 2030 plan also include consumer-IoT (smart speakers, doorbells, etc.) and the smart-appliance end-of-support angle? Existing Claude Reports cover those (`2026-05-19__Petitioning-Strategy-for-Smart-Appliance-End-of-Support.md` and the voice-assistant report).

---

## Sources

- Cycle Final Rules and Registers' Recommendations under `1201/Final Rules/` and `1201/Reg Recommendation/`.
- Consolidated cross-cycle data in `analysis/lineages.json` (Layer 2 of the data layer; see `AGENTS.md`).
- 2024 Final Rule codified text at 37 CFR § 201.40 — particularly (b)(13)–(b)(17) and (b)(21).
- 2021 Class 12 and 2024 Class 5 (broader scope) denial reasoning in the respective Registers' Recommendations.
- Prior strategy work: `1201/Claude Reports/2026-05-19__Petitioning-Strategy-for-Smart-Appliance-End-of-Support.md`.

**Not legal advice.** This plan describes the §1201 rulemaking record and a strategic approach; it is not a legal conclusion. The codified text in each Final Rule is the operative regulation. A petitioner should work with counsel before filing.
