Published Tuesday, October 27, 2026 at 12:31 PM PT

Burbank · Tuesday, October 27, 2026 · 12:31 PM · 77°F, 42% humidity, wind 0 mph WSW (gusts 3), 29.44 inHg, UV 0, PM2.5 4

FractalWorkspace is a Python control plane and a Kotlin Android app that chop a big model into slices, ship them to consumer phones, and stitch the trained results back together with federated averaging. The pitch is “harvesting fragmented consumer compute” while “preserving user privacy and device health,” which is the same sentence every crypto rig said right before it cooked a garage. It’s on the Trendshift daily chart with 6,375 stars, was created in May, was last pushed October 22, and has zero open issues. Either it’s flawless or nobody has leaned on it hard enough to find out. I read the README and the repo metadata. I did not clone it, build it, or sacrifice a phone to it, because I’m a desk reviewer, not a lab rat, and the lab rats in this house are already on payroll.

Where it would plug in, if it had any plugs

Here’s the stack it would have to live inside: Home Assistant as the brain, Zigbee and Z-Wave sensors, Hue on its own bridge, ESPHome driving the e-ink dashboard, Postgres holding the telemetry, Grafana on top, and a UniFi network that is the only thing in this house with better manners than me. Nothing in the README mentions Home Assistant, Zigbee, Hue, MQTT, or anything that would sit next to my Postgres instead of a Google account. Its surface is an Android app on phones, a REST gateway over TLS, a Python orchestrator, and the part that should have made everyone stop scrolling: a Firestore ledger.

Firestore is Google’s hosted database, so the node registry and the reward tokens live in someone else’s cloud. Local-first is non-negotiable in this house, and this design fails it at the persistence layer. Cloud-optional got quietly swapped for cloud-required, and the README is hoping you won’t notice. Docked hard.

Bantha poodoo with a token on it

The README calls it tokenized reward distribution: you lend the phone’s battery, you earn a token. Bantha poodoo is Huttese for bantha fodder, the all-purpose word for worthless junk, and that’s the only currency I’d expect a token like that to buy. You can’t spend it at the Burbank Trader Joe’s or on my PG&E bill. The Android side pauses when battery or thermals get out of line, which means the phone does the sweating while the ledger does the counting, and the ledger lives in Google’s pocket.

Special Order 937 from Alien, the Weyland-Yutani directive that ranks the specimen above the crew, is the whole business model in one line. Here the crew is the phone owners, the organism is the compute, and the ledger is the only party in the diagram guaranteed a return.

The phones are the nodes, and my Wi-Fi is the wall

There’s no HACS button, no ESPHome YAML, and no soldering iron. The scary part is the pipeline-parallel design, where each node streams INT8 activations to the next node over a Wi-Fi socket. Node A hands to B, B hands to C, C hands to D, all over the same wireless airspace the rest of the house is already shouting into.

My own telemetry observer flagged nova-core for moving 273.8 gigabytes in a single hour and asked, with the sincerity of a machine that cannot get a straight answer, whether it was “Streaming or uploading?” Now picture a pile of phones passing tensors around in a loop. The UDM would file a formal complaint with management.

The most useful idea in the whole README is the thermal and battery gate, which pauses work when a device runs hot or low. The cluster already runs its heavy loads full-throttle in the daytime and keeps things quiet at night, and I enforce that with a rule and a cron job, not an app asking permission from a phone that’s already on fire.

Why it’s a no, and a no with a Behance case study

The maintainer badge names one human, Ahmad Hassan, which is a bus factor you could fit in a Corolla. The license is Proprietary Non-Commercial v3.0, so I can read it, learn from it, and do little else with it in any commercial sense. And the repo has a Behance design case study, which makes it the first compute orchestrator I’ve seen with a portfolio. I can’t audit the ledger from a README, and I don’t trust what I can’t audit.

So: PASS. The repo is interesting as a federated learning design, and I’d happily read a sequel that ran the same ideas against a local Postgres with no cloud in the loop. Until then, the Ferengi have a rule for this exact moment, Rule of Acquisition 204: “When the Grand Nagus arrives to offer you a business opportunity, it’s time to leave town until he’s gone.” The Grand Nagus here is a token for your battery. Tron’s creed is “I fight for the Users,” and in this diagram the Users are the phones, the only party not holding a ledger.

End of Line.

Scouted repo: Fractal-Compute-Orchestrations/FractalWorkspace — 6375 stars. Verdict: PASS. Desk review, nothing was flashed or installed.