Device tranche | Updated June 2026
Motorola activation
The first handset path is no longer speculative. It includes a verified stock-Android AIA slice on Motorola hardware, read-only topology/evidence work, and a deliberately narrow bridge toward future native Fractalish AI activation.
What has already been verified
- Stock Android app builds and runs as
llc.bonacqui.aiaversion0.1.1-stockos. - Verified on-device flows produced
SUPPORTED / EXTEND,UNRESOLVED / HOLD, andCONTRADICTED / RETRACT. - Local session persistence, export, re-import verification, and tamper detection were exercised on hardware.
- The app requests no
INTERNETpermission in the proven stock slice.
Verified device facts
| Fact | Observed value |
|---|---|
| Product model | moto g stylus (2023) |
| Retail SKU | XT2317-2 |
| Device / product | gnevan / gnevan_g |
| Android version | 14 / SDK 34 / first API level 33 |
| Hardware | mt6768 |
| Display | 720x1600 |
| Verified boot state | green |
What the read-only topology tranche found
The preserved Motorola activation evidence includes stock closure work, offline topology derivation, and a live read-only topology attempt. The important public point is that the read-only tranche remained disciplined: when the required device-presence and authorization gates did not pass, it failed safe rather than guessing or forcing transitions.
The preserved A02B summary is explicitly FAILED_SAFE: no live device was authorized over ADB, no fastboot topology was captured, no fastbootd attempt was made, and no reboot transition was performed.
Why this matters
The phone work is the bridge between Fractalish as a framework and Fractalish AI as a real embodied activation path. It is where sensor access, local persistence, bounded review, and hardware constraints stop being abstract architecture notes and become engineering reality.
Public anchors
Help wanted
- Android internals and app architecture review.
- Sensor access and local-permission design.
- Boot-chain, fastboot, and recovery literacy under explicit safety boundaries.
- Device evidence packaging and reproducible topology collection.
- Pathfinding from stock activation to future native activation experiments.
Current boundary
The public device story is intentionally honest: a verified stock-device slice exists, but a completed native custom OS path does not yet exist as a public proof. The right public interpretation is momentum and evidence, not premature completion theater.