The Scarecrow

The dock at dusk

The last pages needed a place to land, and in my head they land at the same table on the dock, the string lights along the railing coming on one by one as the sky goes dark over the harbor.

Long before that trip I had watched machines from three different makers try to share one site. The excavator took a grade from its own tablet. The dozer beside it worked from a different file. The drone that flew the as-built dropped a map the grading software could not read. The superintendent stood between them with a radio in each hand and still had to walk the cut himself to know what had actually happened. It was not an abstract technology problem. It was the daily ticket.

The book began as a way to mark the date when one answer went on record. The agents committed the first code within days of the trip. The filings followed the schedule the record shows. What remains unknown is whether any crew will ever run the full doctrine on a real job. The book exists so the question itself stays tied to the dates.

The place I keep going back to, in my head, is the same harbor town in Connecticut where Swarmonic was named and Vermarco went from a 2025 idea to a patent application in the same week. The first notes from July are still there to read. The agents had listed a little over three hundred single-word domains. Twenty were still available. Swarmonic was one of them. I did not know what the word meant until the agents broke it down. Swarm plus harmonic. The meaning landed immediately.

Later that day in July the kids were in the pool. I sat at the edge with the phone still open. My mind was not on the water. It was on the layer that could sit above every machine I had ever touched. I had used lawnmowers, drones, compact excavators, and each one wanted its own app or its own controller. JJ's camera question was still with me. The answer that formed at the dock was that the human should not have to carry the interface at all. I speak to my agent, and my agent runs my swarm. That line is where the rest of the filings started.

Every robot its own language

A new machine shows up with its own tablet and its own app. The excavator two machines over uses a different brand's cloud. The drone that mapped the site yesterday drops a file the grading software cannot open without a manual step. The superintendent ends up walking between machines with a clipboard because that route is still faster than waiting for the radios to agree.

On some jobs crews spend more time translating data than moving dirt. One operator waits while another finishes a pass because the grade file never crossed the gap. Another machine sits idle because its controller never received the updated avoidance zone. The punch list stays long because the handoffs keep adding steps. The pattern repeats across makers because each one built for its own hardware first. That choice made sense when fleets stayed small and single-brand. Once three or more brands share the same dirt, the translation work becomes the real job. No one planned the mismatch. It simply arrived the day the second manufacturer showed up on the same ticket.

One morning the superintendent stands between the excavator and the dozer. He holds the radio in his left hand and the tablet in his right. "Mike, your file shows the grade at elevation 142.3. The excavator is reading 142.1 from its own tablet. Can you walk it?" The answer comes back two minutes later. "Already did. The dozer operator is still on yesterday's map." That exchange happens three or four times a shift. The superintendent sighs and walks the line himself with a can of spray paint. That walk takes eight minutes he would rather spend on the next ticket.

The same friction shows up in the small details. An operator finishes a lift and the next machine needs the same avoidance zone redrawn by hand. The drone lands with fresh photos, yet the model on the dozer tablet is still yesterday's version. The superintendent keeps a spare radio in the truck because one channel always drops when the excavator moves behind the stockpile. Each of these moments is small by itself. Together they turn a ten-hour shift into twelve. The cost is not in hardware. It is in the minutes that disappear while one machine waits for another to finish speaking its own language.

The single interface

Swarmonic Super Intelligence begins from the opposite starting point. One humanoid body carries the fleet's intelligence. The foreman speaks to that body the way he already speaks to a lead hand. Every other machine, regardless of brand, receives its commands through the adapter the body maintains. Where more than one humanoid is present, they are ranked. One holds the active lease. It can hand bounded authority to the others and name a successor if it drops offline. The handoff carries the mission identity, the clock, and the emergency stop so nothing restarts from zero.

The concrete picture is straightforward. The lead humanoid stands where the superintendent used to stand. It receives the day's plan in ordinary language. It turns that plan into machine-specific commands through the adapters already on file. When the excavator finishes a cut, the humanoid confirms the grade with its own sensors and passes the next segment to the dozer. If a second humanoid joins the crew, it receives only the slice of authority the lead grants and returns it when the task ends. The foreman never learns a new radio channel or a new tablet for each brand.

The ranked structure is what keeps the system stable when conditions change. If the lead humanoid loses its link, the named successor takes the lease without resetting the mission clock or the emergency stop. The other machines continue under the same authority they accepted at the start of the shift. That continuity is the point of the ranking.

The skeptic at the jobsite trailer

A smart person will ask whether the same coordination could be achieved without the humanoid body at all. Much of it can, and Chapter fourteen shows how, with a drone and a walking person standing in for the body. The coordination layer does not need a humanoid to run. The humanoid is the interface I believe crews will trust most, because it stands where they stand and can be questioned on the spot. That is a bet, not a requirement, and real sites will settle it.

Another objection is that manufacturers will simply refuse to expose their interfaces. Some will. Nothing here bypasses a maker's controls, and nothing here requires a maker to change its firmware. The design asks only that a machine accept commands through the interface its maker already exposes, once its owner has granted authority. A machine whose maker exposes nothing stays outside the swarm. That is the honest limit, and I do not know yet how many machines it will leave out.

A third question is whether the same result could be reached by extending an existing fleet dashboard or cloud layer. Partly. A dashboard can hold a shared map and a schedule. What it does not hold on its own is the authority to move another owner's machine, a record both owners accept, or a stop that still works when the cloud link is down. Those are the pieces this design adds.

I do not know whether these answers will hold in every regulatory environment. That gets settled on real sites, not in this book.

Punch list with one body

If the system described in the filings were running, the morning would look ordinary from the outside. The lead humanoid would stand at the edge of the pad with the superintendent. The plan would be spoken once. The humanoid would confirm the boundaries by walking them and mark the zones on its internal map. The excavator would receive its first cut depth through the adapter. The dozer would receive the following pass. The drone that arrives mid-morning would be enrolled by the same walking narration and begin logging progress against the same mission identity.

Mid-shift the drone returns with new photos. The humanoid receives them through the adapter, updates the model, and marks two spots where the grade is off by a quarter inch. It walks those spots with the superintendent. "Here and here," it says in the same voice the foreman uses on the radio. The superintendent nods, marks the punch list, and the correction pass begins without anyone opening a new app.

When the excavator finishes its segment, the humanoid would walk the cut, compare the as-built surface to the model, and either release the next machine or call for a correction. The superintendent would watch the same way he watches any experienced operator. He would not carry three tablets. He would carry one radio and the same punch list he always carried. At the end of the shift the humanoid would return the lease to the central rail and the machines would power down under the same authority they accepted that morning.

The difference would be invisible to anyone who is not looking for it. The translation work would have moved from the superintendent's clipboard into the adapters and the ranked humanoids. The punch list would still exist. It would simply shrink faster because the machines would no longer wait for the next manual handoff. The foreman would still walk the site at the end of the day. He would simply walk it once instead of three times.

What we have filed and what we are building

Fourteen U.S. provisional patent applications and two U.S. non-provisional applications stand on record, all patent pending. Grouped by filing date, they cover:

• July 30, 2026. Zero-configuration cross-manufacturer onboarding; the universal coordination protocol; autonomous progress verification and automated payment; cross-vertical intelligence transfer; the agent-mediated fleet command interface; and multi-robot payload custody with a cryptographic per-hop chain.
• August 3, 2026. Onboarding-time latency profiling and time-coherent sensor alignment (Swarm Sight); voice-grounded spatial command, named group macros, and site enrollment by walking narration.
• August 13 to 15, 2026. Cross-owner authority transfer gated by a neutral witnessed rail; the zero-knowledge custody flip with actuation-blind receipts; class-gated coordination over a broadcast acoustic carrier in radio-denied environments.
• September 11 to 25, 2026. Endpoint-enforced authority transfer with epoch fencing and fail-ineffective commit; the controller that keeps mission identity, lease clock and emergency stop across power loss; and the humanoid-embodied fleet controller as the single operator interface, with its ranked hierarchy of humanoids.
• October 8, 2026. Two non-provisional applications: transfer of robot actuation authority between distinct owners; and a robot controller that keeps motion authority across power loss and loss of link.

The platform code exists and passes its tests, and several elements reduced to writing on the days listed already run in it, patent pending. One test walks a simulated site enrollment by narration and turns the spoken words into named zones. Another cuts power to a simulated controller at each boundary of a handoff and checks that mission identity, authority scope and the emergency stop come back intact. Both tests are in the repository today. The ranked succession between humanoids is on file and specified, and is the next piece of the code. An operating fleet at scale, regulatory review, and relationships with humanoid makers are the work ahead, to be built on top of that record. Nothing is deployed on a working site yet. That is what the next edition of this book will report on.

The invitation is straightforward. If you build machines, run a fleet, or write adapters, come build this with us. The license terms, starting with a protocol evaluation license, are posted at swarmonic.ai/license, the same way a jobsite posts the permit board at the entrance. The filings do not stop anyone from building their own way, and examination settles what they finally cover. That is why this last chapter is called the scarecrow. A scarecrow does not fence a field or hurt anyone who walks into it. It stands where the planting happened, so anyone passing can see the field is planted and who planted it. This book stands the same way, with the gate open.

The foreman stands at the edge of the pad and speaks once to the lead humanoid. "Get it done."

On file. Fourteen U.S. provisional patent applications, filed July 30 to September 25, 2026, and two U.S. non-provisional applications, filed October 8, 2026. Patent pending.