Equation 3 · Small and On-Device AI in 2035: Scenarios and Falsifiers
What does this equation mean?
Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.
This equation states a bound: one expression must stay on the indicated side of the other under the article’s assumptions. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.
Read it piece by piece
Symbol D
D is part of the quantity the equation computes from the expression on the right.
Symbol t
t is an argument of the function-like quantity on the left; its role is set by that function’s stated inputs.
Symbol P
P is one factor in the product that computes the quantity on the left.
Symbol p^*
is one factor in the product that computes the quantity on the left.
Symbol L
L is one factor in the product that computes the quantity on the left.
=
The expressions on both sides represent the same quantity under the stated assumptions.
See an illustrated explanation →superscript
A raised number can be a power. When it is a label or bound, it selects a case or the upper limit of a sum; the formula’s structure distinguishes these uses.
See an illustrated explanation →How to interpret it
Read it with the definitions, units, and assumptions supplied by the article.
What the article says around this equation
Whether on-device AI becomes the default computing substrate for everyday tasks — the thing a phone or a laptop does locally as a matter of course, with the cloud as the exception rather than the rule — is not a third axis; it is what the other two jointly produce, and testing that jointness is exactly what the room’s validation bench exists to do. Write P(t) for the share of everyday-task requests an on-device model can handle at rough parity with a cloud-frontier model — Axis A’s own proxy — and L(t) for the share of deployments where on-device personalization is reliable enough that a user or an operator trusts it without a cloud fallback — Axis B’s own proxy. A device that is fast but…
Read the full surrounding passage
Whether on-device AI becomes the default computing substrate for everyday tasks — the thing a phone or a laptop does locally as a matter of course, with the cloud as the exception rather than the rule — is not a third axis; it is what the other two jointly produce, and testing that jointness is exactly what the room’s validation bench exists to do. Write P(t) for the share of everyday-task requests an on-device model can handle at rough parity with a cloud-frontier model — Axis A’s own proxy — and L(t) for the share of deployments where on-device personalization is reliable enough that a user or an operator trusts it without a cloud fallback — Axis B’s own proxy. A device that is fast but generic still routes anything that needs to know the user to the cloud; a device that personalizes beautifully but cannot match cloud capability on hard tasks still routes those tasks out. Becoming the default substrate needs both conditions at once, not an average of them: . D(t) stays at zero however high either term climbs alone. Axis A determines whether P(t) can plausibly clear within this article’s horizon; Axis B determines whether L(t) can. Neither can be inferred from the other, which is why they are kept as two axes rather than folded into one.
Sources cited in the article section
These citations give research context. Read each source to check which claims it supports.
Return to Small and On-Device AI in 2035: Scenarios and Falsifiers