The phone as a runner, one tap: the WASM tier issue #8 open andymccall opened this · 1 comment
andymccall set labels feature, runner ·
Planned with Andy (2026-10-25): oxygenflow docs/handover.md. This runner needs the WASM tier first (oxygenflow#75, not built yet), then drain (oxygenflow#76) so leaving the charger or the allowed network hands the job back instead of losing it. The runner is Flow's runner code built for Android through rust-core (uniffi) with wasmtime, in a foreground service; trust class device (oxygenflow#79). First demonstration (handover.md §11): plex builds oxy-core's tests for wasm32-wasip1, the phone runs them; Wi-Fi off halfway and plex-1 takes the job over.
referenced by 5 changes on 25 Oct 2026
4aee5293461d 74bbbc259910 ff65ea456ff1 114865a07877 41e2e862abce
andymccall referenced by change ed6c64d23fca on main ·
andymccall referenced by change 8440d51a2275 on main ·
andymccall referenced by change 0b152017dee3 on main ·
Once signed in, one tap registers the phone as an OxygenFlow runner (arm64, label android) running the WASM tier inside the app, as a foreground service. Runs only when allowed: on charge, on Wi-Fi, under a temperature, within a storage budget the owner sets; pauses on battery or heat; shows what it runs. Scoped like any runner (site, organisation, repository).