Measured product lead custody receipt.
github.com/Zer0pa/DM3RESEARCH-READY
LIVE
R8 OPEN
Mobile Deterministic Geometric Computation
When two phones run the same code, the numbers should match — DM3 · github.com/Zer0pa/DM3
Every AI app on a phone depends on the chip doing the same thing each time, but almost no one checks. Two phones can run the same model and quietly return different numbers, and the gap stays invisible. DM3 fixes a small computation in place — one binary, one 380-vertex graph — and runs it on two physically distinct Android ARM64 phones. At five measured steps, both phones return identical bytes.
Seven of eight reconstruction checks close. The eighth is still open, and other chips are out of scope.
01 · THE GAPNO RECEIPT
Two phones, same computation, different chips; nobody checks whether the numbers actually match.
02 · MARKETSADJACENT FORECASTS
Five neighbouring markets, one unmeasured assumption: phones that quietly disagree on the same calculation, and nobody priced the cost.
03 · VALUE
$173.5B
The 2031 on-device AI market — built on a chip-level sameness nobody has been checking.
04 · INSIGHT
Same task. Same chip family; same bytes.
05.1 · CURRENT TECHNO RECEIPT TO CHECK
Two phones run the same model and return slightly different numbers. The gap gets blamed on chips, on rounding, on luck — and then it gets shipped. Nobody can point at the step where the two phones first disagreed.
05.2 · OUR TECHBYTE-EXACT REPLAY
DM3 pins a small computation — one Android binary, one 380-vertex graph, twelve callable task modes — and runs it on two physically distinct ARM64 phones, a RealMe RM10 on native Android and an Apple M1 on an Android emulator. At five measured steps, both phones return identical bytes. A mismatch would have a step number, not a shrug.
05.3 · BENCHMARKSCHECKED PACKET 2026-04-22
Steps5/5matches
ScopeARM64only
DevicesRM10vs M1 AVD
Checked202604-22
Scope: ARM64 only, one task configuration, steps {20, 30, 40, 45, 50}; the eighth reconstruction step is still open.
06 · MEASUREMENTSHA-256 RECEIPT CHAIN
When two phones disagree, the disagreement has a step number.
06.1 · COMPARATIVE PERFORMANCE · SHA RECEIPT ON STATIC TIER-2
Checked 2026-04-22. A RealMe RM10 on native Android and an Apple M1 Android ARM64 emulator return identical hashes at steps 20, 30, 40, 45, and 50. Three ARM64 platforms confirm; Intel chips were out of scope and are not claimed.
07 · KEY METRICSDM3 CHECKED PACK
07.1 · ARM64 MATCH
5/5
Identical-byte steps · two physically distinct phones
07.2 · SIGMA SHAPE
3/3
Three ARM64 platforms agree · on every step's trajectory
07.3 · CALLABLE TASKS
12
Distinct tasks the fixed binary will run · on demand
07.4 · STATE DIMENSION
72,960D
Floating-point numbers compared · per step, per phone
07.5 · RECONSTRUCTION
7/8
Reconstruction checks closed · the eighth still open
08 · DETERMINISMSHA-PROVEN ARM64
Two phones. Same bytes; a hash decides.
08.1 · WHAT DETERMINISTIC MEANSBYTE-EXACT TRAJECTORY
At every measured step, the same geometric computation produces identical 64-bit floats on two physically distinct ARM64 phones — a RealMe RM10 on native Android and an Apple M1 Android ARM64 emulator. The cryptographic hash over the trajectory matches at steps 20, 30, 40, 45, and 50.
Determinism here means byte-identical, not approximately equal. The scope is one task configuration on Android ARM64. DM3 does not claim Intel CPU, GPU, or neural-accelerator parity. The check is reproducible, narrow, and dated.
08.2 · THE HONEST BLOCKER
Honest Blocker ·
R8, the eighth reconstruction step, is still open. The packet is scoped to 2026-04-22, and four later evaluation cells (G.3, G.4, G.5, G.7) have no promoted outcomes. ARM64 agreement does not imply Intel, GPU, or accelerator agreement. DM3 is a diagnostic, not a framework. Independent source-code provenance for the binary is not yet attestable.
09
WHEN PHONES STOP quietly disagreeing.
09.1 · THE AMBITION
A mobile AI app should compute the same answer on every phone it runs on. Today that is a wish; DM3 narrows the wish to one fixed binary and one fixed graph so the answer can be tested. Once two phones agree to the byte, sameness becomes something a buyer can require.
09.2 · WHAT WORKS NOW
What holds today: two ARM64 phones return identical bytes at five measured steps; seven of eight reconstruction checks close.
09.3 · WHAT'S STILL OPEN
Still open: the eighth reconstruction step, Intel and GPU parity, source-code provenance, and four later evaluation cells.
09.4 · DEBUGGING · NEAR-TERM (12–24 MO)
A mobile bug stops being folklore
A mobile engineer staring at two phones that disagree on the same model output can now point at the exact step where they diverged. The argument with the chip vendor moves from "it feels off" to a numbered cell.
09.5 · PROCUREMENT · NEAR-TERM (12–24 MO)
A device buyer can require sameness
An enterprise procurement team specifying a fleet of ARM64 phones for inspectors, medics, or field auditors can write the same-bytes requirement into the purchase order. Acceptance testing has a number to pass, not a vendor narrative to trust.
09.6 · CERTIFICATION · MID-TERM (24–48 MO)
Mobile AI claims gain a unit
A regulator reviewing an AI-powered medical or safety app on a phone gets a primitive to ask for: does this computation match across the certified device class? Without it, every claim about "the model" is a claim about an unbounded number of devices.
09.7 · STANDARDS · MID-TERM (24–48 MO)
Industry benchmarks gain a floor
A mobile-AI benchmark consortium that adopts a fixed-binary, fixed-graph cross-device check stops publishing leaderboards where the same model scores differently per chip without explanation. Comparative results recover their meaning.
09.8 · METROLOGY · PARADIGM (48 MO+)
Computation joins the measured world
A computation that any independent lab can rerun and get the identical bytes back is closer to a kilogram than to a screenshot. Over time, courts, auditors, and scientific reviewers can point at a retained execution event the way they point at a sample on a scale.