Problem
Phone compute could easily expose a general command surface.
Arbitrary commands, unchecked host identity, public traffic, and silent local fallback would make the experiment unsafe and the result hard to trust.
Independent build · LAN systems lab
Use an Android phone as a narrow Ubuntu compute node—not a remote shell.
A Windows controller selects a known job, Ubuntu hosted through Termux runs it, and validated results return over a trusted LAN.
Build
The controller sends a job name, not a shell command.
I built allow-listed health, benchmark, smoke, and fixed compute jobs with strict host checks, validated JSON, location markers, and bounded async retrieval.
Result
The artifact proves where it ran and whether it changed.
Windows and Ubuntu use the same benchmark source. Returned artifacts are accepted only after schema, size, and SHA-256 checks.
Before / after
Resolve a known job before the network.
Broken
result = ssh.run(request.command)
return resultFixed
job = ALLOWED_JOBS.get(request.job_id)
if job is None: reject("unknown job")
result = ssh.run(job.fixed_entrypoint)
validate_json(result)
verify_size_and_sha256(result.artifact)Evidence
The lab records execution, output shape, and artifact identity.
- Health and smoke jobs return validated JSON with execution-location markers.
- Benchmarks use the same source on Windows and phone-hosted Ubuntu.
- Returned artifacts are checked against byte size and SHA-256.
Stack and capabilities
Cross-platform orchestration with small contracts.
- PowerShell
- Python
- SSH
- Termux
- Ubuntu
- JSON validation
- SHA-256
Next