DimOS Hackathon · experimental · 2026
Every team makes robot dogs that share a map.
We made them share a mind.
the problem
Two dogs = two SLAM origins. To share one map you must fuse frames — fragile, and it breaks the moment a loop closes wrong.
Map-merge is weeks-to-months of engineering before any coordination happens. Wrong layer to build on in 48 hours.
Skip the map. Let each dog keep its own. Share only meaning — what's searched, what's found. Share a mind, not a map.
The whole bet: the useful thing to share between robots is operational memory, not geometry.
the insight
static partition (left) can't adapt · shared memory (right) rebalances
Alpha→NORTH, Bravo→MIDDLE, Charlie→SOUTH. One finishes early and sits idle. One goes offline and its region is never searched. Indistinguishable from a hardcoded script.
Any body writes what it sees; any body reads and acts. Who-does-what emerges from who's free and what memory says — and it survives a robot dropping.
how it works
one shared map + zone ledger · the A/B knob = share one memory, or each dog keeps its own
what makes it magic
Alpha finds the target and writes it to the pack's memory. I ask Bravo — which was never there — and Bravo walks straight to it. One sees, the whole pack knows.
Take the finder offline. Its findings persist and its unsearched ground is reclaimed by the survivor. A database doesn't do that — roles are emergent and fungible.
Alpha saw it. Bravo remembered it. The pack acted. One memory, many bodies.
the proof · sim A/B, same dogs, same start
The honest claim: complete-area coverage, faster & without re-search — and robot-failure tolerance. Not "races to the object faster."
why this is worth money
Cheaper · longer battery · more agile. Every vendor races on the same axes — a sprint to the bottom. The dog is a replaceable body.
Fleet memory · mission intelligence · shared semantic blackboard. Value grows with fleet size and runtime — hardware-agnostic.
Run it long enough and the site itself becomes legible — recurring anomalies, chronic blind spots, high-risk hours. Hardware keeps getting cheaper; spatial operating memory only gets more valuable.
where it lands
Factories · warehouses · campuses · data centers. Shared patrol record, auto incident reports, no re-patrol.
Who's nearest? Enough battery? Which zone unchecked? Highest-priority task — assigned straight from shared memory.
Spatial risk maps · recurring-fault analysis · cross-shift knowledge transfer. The site's long-term operating memory.
the one image to remember
One memory. Many bodies. That's Pack Mind.