Do right-to-repair laws apply to a device just because it has AI in it?

Coverage generally turns on the product category, the sale date and the customer type rather than on the technology inside. Several state fair-repair statutes reach consumer electronics broadly, with carve-outs that commonly include motor vehicles, medical devices, agricultural and heavy equipment, video game consoles and some enterprise or public-safety equipment. The practical question for an AI hardware company is not whether the model is regulated but whether the enclosure it ships in falls inside a covered category — a camera with on-device inference is usually just a camera for these purposes.

Is parts pairing itself unlawful?

It depends on the state and on what the pairing does. The strongest provisions prohibit designing a device so that an otherwise functional replacement part is disabled or has features degraded, and prohibit displaying misleading warnings about unidentified parts. Others require only that the manufacturer make available whatever tool or credential is needed to complete the pairing, on fair and reasonable terms. A manufacturer operating nationally usually ends up building to the stricter rule, because maintaining two firmware behaviours by shipping address is worse than one compliant pathway.

Does 'tools and documentation' include a calibration utility?

That is the central question for AI hardware, and the answer is usually yes where the utility is needed to return the device to fully functional condition. These statutes typically define tools to include software tools, and require that documentation, parts and tools be made available to independent providers on terms no less favourable than those offered to authorised ones. A sensor swap that leaves the device physically repaired but functionally degraded until an internal calibration routine runs has not been completed, and the routine is the tool.

Can we withhold model weights or inference code as a trade secret?

The obligation is generally to enable repair, not to disclose intellectual property, and these laws typically do not require divulging trade secrets or source code. Weights, training data and inference implementations sit comfortably on the protected side. The distinction that matters is between the model and the provisioning: refusing to publish weights is defensible, while refusing to let a replacement module receive the standard signed model bundle that every authorised repair applies is a repair restriction dressed as an IP position.

What about safety — some calibrations really do matter?

Safety is a legitimate design consideration and several statutes acknowledge it, but it functions poorly as a blanket justification. The defensible version is specific: a named hazard, an objective post-repair verification the device performs and reports, and an equal pathway for independent providers to satisfy it. The indefensible version withholds the verification entirely from independent providers while authorised ones run it routinely, which asserts that the same procedure is safe in one pair of hands and unsafe in another.

Where does the compliance failure usually show up first?

In marketing copy and support content rather than in firmware. Product pages promising a device is user-serviceable, help articles warning that unauthorised parts will damage the device, warranty language implying that independent service voids coverage, and end-of-life notices quietly withdrawing a required download are all cheap to publish and durable once indexed. They are also the artefacts an enforcement inquiry or a plaintiff reads first, because they are public and dated.

The Sensor Is Fine. The Model Won't Accept It.

Six Layers, and Where Each One Locks

Read a device as a stack rather than as an object. Repair obligations were designed for the top of it; AI products put the decisive dependencies at the bottom, where no screwdriver reaches.

L6MechanicalTraditional scope

In the product

Enclosure, fasteners, connectors, replaceable modules

What stops the repair

Adhesive, proprietary fasteners, non-modular assembly

L5FirmwareCovered where a tool exists

In the product

Boot chain, signed images, device identity

What stops the repair

Signed-image checks that reject an unsigned but genuine module

L4Pairing / attestationDirect exposure

In the product

Serial binding of camera, battery, sensor or biometric module

What stops the repair

Feature degradation or nag warnings after a genuine part swap

L3CalibrationDirect exposure

In the product

Lens distortion maps, mic array geometry, thermal offsets, IMU zeroing

What stops the repair

Calibration routine only exists in an authorised-service utility

L2On-device modelSplit — weights protected, provisioning is not

In the product

Quantised weights, per-device tuning, inference runtime

What stops the repair

Model bundle re-provisioning gated behind a service account

L1Cloud dependencyRepair restriction in effect

In the product

Activation, licence check, feature flags, telemetry

What stops the repair

Repaired device cannot re-activate without manufacturer approval

The Parity Test Nobody Runs Internally

The statutory standard is comparative, so the internal audit should be too. List what an authorised technician receives, list what an independent one can obtain today, and look at the rows where they differ. Every gap below is one a company can close by decision; none of them requires disclosing a model.

Repair input

Authorised

Independent

Service documentation and schematics-level repair guidance

Full

Often summarised or withheld

Replacement modules sold individually rather than as an assembly

Full

Frequently assembly-only at a price near a new unit

Diagnostic utility that reads sensor health and fault codes

Full

Usually the first thing gated behind a service login

Calibration routine after a sensor or optical module swap

Full

Rarely available — the most common functional gap

Pairing / attestation credential for a genuine replacement part

Automatic

Often no pathway at all

Model bundle re-provisioning after board replacement

Automatic

Undefined; device ships degraded

Firmware images for the version the customer is actually running

Full

Latest-only, which can break a fleet on an older validated build

Calibration Is Not a Trade Secret

The strongest argument a manufacturer has is that model weights and inference code are protected intellectual property, and it is a good argument. It does not extend as far as it is usually stretched. A lens-distortion calibration routine, a microphone-array geometry fit, a thermal offset table or a per-device zeroing pass are procedures a device runs on itself. Withholding them does not protect a model; it prevents a repair from completing, which is the conduct these statutes were written to reach.

The same distinction sorts most other cases cleanly. Publishing weights: not required. Letting a genuine replacement main board receive the standard signed model bundle that every authorised repair applies: hard to characterise as anything but a repair pathway. A company that draws the line at provisioning rather than at disclosure keeps its intellectual property and loses very little else.

Six Things to Build Before Anyone Asks

01Publish a repair page that states, by product and model year, what documentation, parts, tools and software are available and how an independent provider obtains each one.

02Split the service utility into a repair-completion tier — diagnostics, calibration, pairing, provisioning — and an internal tier, then make the first tier obtainable without an authorisation relationship.

03Remove feature degradation and non-genuine-part warnings that fire on a functional genuine part, and reserve alerts for parts the device can objectively show are faulty or counterfeit.

04Sell the smallest replaceable unit the design supports; assembly-only pricing is the most visible form of practical repair prevention.

05Commit in writing to a parts and firmware availability window that outlives the sales window, and honour it through end-of-life rather than letting a download quietly 404.

06Audit warranty, support and marketing copy for language implying independent repair voids coverage — the statutory obligation and the consumer-warranty rule both point the same way.

The Documentation Cliff at End of Life

The failure that hurts customers most is not a refusal but an expiry. A support page is retired, an activation endpoint is decommissioned, a firmware bundle stops being served, and devices that were repairable last year are not. Where a product's core function depends on a cloud call, end-of-life planning is a repair obligation and a consumer-protection question at the same time, and the commitment is worth far more in writing at launch than in a decision made by an infrastructure cleanup ticket.

Audit What Your Product Pages Promise About Service

"User-serviceable", "lifetime updates", "authorised service only" and warranty language written by three different teams tend to contradict both each other and the repair pathway you actually offer.

See every claim across your site in one pass. Run a free scan and reconcile it with your published repair policy.

This article is general information and not legal advice. Right-to-repair obligations differ substantially by state in covered product categories, sale-date thresholds and parts-pairing restrictions, and several carve-outs apply. Consult qualified counsel before relying on any conclusion here.

Six Layers, and Where Each One Locks

The Parity Test Nobody Runs Internally

Calibration Is Not a Trade Secret

Six Things to Build Before Anyone Asks

The Documentation Cliff at End of Life

Related Reading

Audit What Your Product Pages Promise About Service