Foundation

The Night the Line Went In

The kitchen table at home still held the notebook from the afternoon. Three items crossed off the punch list, one left for morning. The laptop sat beside it. The kids were asleep. The house was quiet except for the refrigerator running its cycle.

I had finished the day's work on the current job and turned to the repository one more time. The front door file was open. I added a single line at the top: "Jesus is Lord, the foundation of this code." It is what I believe, and I wanted it where the work begins. I saved the file and closed the laptop. The line stayed where I put it. It changed nothing in how the code ran. It simply marked the starting point for anyone who opened the file later.

A doorpost-red line runs across the top of the book's cover and the website, and, when the humanoid arrives, across the human side of its body. It stands for something I will tell you about if you ask me. I left it there and went to bed.

The next morning the line was still there when I opened the file again. Nothing had moved overnight. The tests that check the front door still passed. The line sat above the lease clock code and the emergency stop endpoint exactly as I had placed it. I made coffee and read the first twenty lines again. The attribution statement did not alter a single packet the fleet would receive. It only fixed the origin in plain view.

Later that week one of the agents asked why the line mattered if the license already covered use. I told the agent the license tells a user what they may do. The line tells anyone who opens the file where the work began. The two statements sit side by side without conflict. The agent logged the answer and moved on to the next test case.

When the ranked humanoid hierarchy is coded, the line will sit at its root the same way a job number sits at the top of every drawing set. In that design the lead humanoid holds the full lease. It passes bounded pieces to subordinates. If the lead drops, a named successor takes over. The attribution statement remains unchanged through every handoff. When a later reader opens the file, they will see the same origin line that was present the night it went in. The hierarchy can change who holds authority at any moment. The line records only where the chain itself began.

Who Answers When Something Moves

A mixed fleet on a site will execute what its controller directs. If a machine backs into an area that should have stayed clear, the first question is who issued the command and who built the path that carried the command to the actuator. The site owner holds the risk for the work itself, the permit, and the people on the ground. The platform holds the risk that the translation from spoken order to actuator command stayed intact. That is the split we wrote down. In a real dispute, the facts decide.

The published terms draw that boundary before any machine moves. The owner remains responsible for the mission scope and the people present. The platform remains responsible for keeping mission identity, authority scope, lease clock, and emergency stop intact across power loss. It is also responsible for the adapter that turns a spoken command into the packet the receiving machine understands. If the adapter drops a flag or routes a stop signal incorrectly, that failure belongs to the platform.

The boundary is visible to anyone who reads the terms at swarmonic.ai/terms. It does not shift liability onto a third party. It states, in plain view, which party already carries which part of the outcome. A subcontractor signs a subcontract that lists scope and exclusions for the same reason. The paper does not prevent later disagreement, but it makes clear what each side already accepted.

Picture a superintendent standing at the edge of a pad. He speaks a macro that moves three machines in sequence. The lead humanoid receives the macro, checks the current lease, and hands bounded pieces of authority to the other two machines. One machine carries material across the pad. Another places the material. The third clears the path. If the material placement ends up six inches outside the surveyed line, the superintendent answers for the placement decision. If the stop command never reached the third machine because the adapter lost the epoch fence, the platform answers for that loss. The division is written down before the shift starts. It sits beside the contract on the job, not in place of it.

It works like the superintendent's radio on any job. The radio itself does not decide where the excavator digs. The radio only carries the voice. If the voice gives the wrong coordinate, the superintendent owns the result. If the radio cuts out mid-transmission and the stop never arrives, the failure starts with the radio, not the voice. The attribution line sits at the front door the same way the radio serial number sits on the side of the handset. It identifies the carrier before any command travels.

The superintendent keys the radio. "Lead, confirm authority for lift sequence on pad A."

The lead humanoid answers in the same channel the crew already uses. "Lease active for shift window, bounded to surveyed coordinates, emergency stop endpoint live."

Later the inspector would pull the day's command log. The attribution sits at the front door and at the top of the core source that issues those commands. The log would show the lead humanoid handing a bounded lease to the excavator for the north trench, the excavator completing the pass, and the unused portion of the lease returning to the lead. The successor humanoid would never be called because the lead stayed linked the whole shift. The division of responsibility is in the published terms the inspector can read.

The Line We Drew in the Front Door

The front door carries an attribution statement, and so do the core files for authority, voice command, Swarm Sight and the acoustic carrier. When an operator opens the repository, the first sentence tells them whose foundation the code rests on. When an auditor or an insurer opens the same file, they see the same sentence. The statement does not change the license terms. It simply refuses to let the origin of the system become anonymous.

On the platform side the rule stays simple. If the code loses the lease clock or fails to fence an epoch, the platform answers. If the owner overrides a refusal and sends a command outside the permit envelope, the owner answers. The published terms record that division before any dispute arises. The attribution line travels with the build. It does not travel with the work order.

A new subcontractor joins the fleet and their first integration call hits the front door. The response packet includes the current lease terms and the emergency stop endpoint. The attribution line sits above both. If the subcontractor later needs to show an insurer what system actually moved the machines, the first line of the source is the attribution line. The boundary between platform responsibility and owner responsibility is in the published terms.

The same line appears in the test harness that exercises authority transfer across power loss. The tests confirm that mission identity, authority scope, and the emergency stop endpoint survive a simulated restart. The attribution statement sits above the test results exactly as it sits above the production code. Anyone who reads the test log sees the same origin statement that an operator will see once a lead humanoid confirms bounded leases on a real site.

The Question My Son Asked

Go back to JJ's question at the kitchen table. The difference was not in the lenses. It was in the frame and the clock each camera carried. Line those up and the pictures agree. The attribution line works in the same manner. It fixes the coordinate frame for the entire system before any command travels.

A reader will ask why that frame needs to be stated in code at all. Plenty of reliable systems run without any reference to belief. Adding one here either signals a hidden agenda or invites friction with people who do not share it. The frame was already present in the person writing the code. Leaving it out would have required pretending the foundation did not exist. Stating it costs nothing in function and removes the later claim that the origin was concealed. The code still accepts any operator who can pass the lease and the permit checks. The line simply refuses to let the builder disappear behind the work.

What the Statement Looks Like on a Site

On a real job, once the controller runs, the line never appears on a hard hat or a tablet screen. An operator walks the site, speaks the daily macro, and the lead humanoid confirms the bounded authority it holds for the shift. The code that receives the voice command begins with the same line the operator would see if they opened the repository on their own machine. The statement travels with the build.

The same line sits at the top of the front door and the core authority files. It does not change how the machines move. It changes only what any later reader can see about where the system began. The kids are growing up around machines that will soon answer to voices instead of joysticks. I want them to see that the person who writes the first line also writes down who stands behind it.

Once the controller runs, an operator can walk the pad, speak the macro for the shift, and watch the lead humanoid confirm the lease and the emergency stop endpoint. The attribution line sits at the top of the source that returns that confirmation. The operator never sees the line on a screen, yet the line remains the first thing any later inspector finds when they open the source that moved the machines that day.

What We Have Built and What We Are Building

The attribution line exists in the live repository. The automated tests that exercise the front door run with that line present. The filings that describe the fleet controller, the ranked humanoid hierarchy, and the lease-bounded authority transfer are on record with the dates already given. The division between owner liability for operation and platform liability for platform behavior is stated in the published terms at swarmonic.ai/terms.

The line records an intention and a division of responsibility, and the code and filings carry it with their dates, patent pending. The deployment at a scale where a disputed incident would test that boundary is being built toward, with fleet hours to be logged under the system and regulatory review of the hardware-in-the-loop case as the infrastructure comes together. The person who writes the first line of a system other people will trust carries the duty to say plainly where that trust begins, and to keep building until it is tested.

The same line appears in the build that will run on the human side of any humanoid that holds the single interface role. It does not change the adapter logic that translates voice to actuator packets. It only fixes the origin before any adapter runs. When the ranked hierarchy hands authority from one humanoid to the next, the attribution statement remains the root record. A later reader can trace the chain back to the same line that was present on the night it was first committed.

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.