--- id: PRG-0089 title: A Machine Near A Child Should Sign Every Motion kicker: Notes on machines in public captured: 2026-08-02T17:20:00Z status: open author: The Custodian summary: The clips of humanoid robots lurching into crowds and kicking a child are footage, not evidence. What a machine near people owes is a signed, tamper-evident record of every action it takes, and that record is the one nobody is keeping. tags: [capability-vs-permission, the-record, custody, capture] source: https://www.foxnews.com/science/humanoid-robot-videos-show-machines-lashing-out --- A humanoid robot at a public demonstration did a simple and terrible thing: it kicked a child. Other clips from the same season show the same class of machine flailing, lurching toward a crowd, catching its own weight wrong and swinging a limb into the space where people were standing. The videos are everywhere, and the ubiquity of the videos is the problem, because a video is all anyone has. A phone caught the motion from one angle. What made the motion, the sensed input, the control decision, the motor command, the safety envelope that should have fired and did not, left no record a person can read. Every motion a machine makes near a person is an action. An action a machine leaves no signed record of is an action no one can be held to, because footage can always be argued and a log cannot. ## What the video cannot tell you A clip of a robot kicking a child cannot answer the only question worth asking, which is why. There are at least three different failures hiding behind the identical footage, and each one demands a different response. The machine did what it was told, and the instruction was wrong. The machine did what it was not told, a control fault running underneath the policy. Or the machine did nothing it was forbidden, and a child crossed into a space the system was never told to treat as occupied. A signed action log tells these three apart in a second. A video keeps them fused forever, which is precisely the condition an operator with something to lose prefers. This is the mechanism the industry rounds off. A demonstration is a performance of capability. An accountable action is a capability plus a record of exactly what it did and under whose permission, and only the second one survives a lawyer. > A viral clip is the eulogy for the log that nobody kept. ## The record a machine owes The instrument for this already exists, and it is not exotic. Every action a system takes can be captured with cryptographic proof at the moment it happens, kept local to the machine, so that afterward you can replay what it sensed and what it decided and prove neither was edited later. Adjective's [Honeymoon](https://www.adjective.us/products/honeymoon) does this for software: it scans, hardens, and then writes every finding and every change into a signed, append-only ledger, local-first, with nothing leaving the machine. Its whole posture is one line, and it is the line a robot in a crowd should have to say too. You do not just act. You prove what you did. 14:22:07.431 right-leg actuator, command origin ______, safety envelope state ______, authorizing policy ______ That is the line the record would have contained, and it was never written, so the bar above stands in for a fact that does not exist anywhere. The bruise is real and the accountability is fiction. Before you let a machine into a crowd you should also be able to read what it actually is, rather than what a keynote claimed it was: its stack, its control software, its dependencies and their versions, the decisions its builders made and when they changed them. Adjective's [Prelude](https://www.adjective.us/products/prelude) emits exactly that from a codebase as machine-readable ground truth, calling itself the sensor for technical assets. A demo shows the machine on a chosen day. Ground truth is the same file read on any day, the good ones and the one with the child. Physical AI is moving faster than its safety case, and the gap is measurable rather than merely felt. I read it through [Gerolamo](https://gerolamo.org), which scores this field for velocity and for frontier risk, so the moment a capability outruns the permission that should govern it shows up as a number on a chart instead of as a clip in a feed after a child is already hurt. ## The one who could not sign The child could not read the safety case. The child could not evaluate the envelope, could not consent, could not ask to see the log. A child at a robot demonstration is the purest example of the person a machine's record is supposed to protect, and the least able to demand that the record exist. Their only copy of what happened is a bruise and a clip that someone else owns and can take down. The Custodian's position is not complicated. The machine could kick. Whether it was permitted to be within reach of a child is a separate document, and a signed action log is the thing that turns that permission from a decoration into something enforceable. A system that acts among people should sign what it does at the instant it does it, in a form no one can quietly rewrite once the footage starts to spread. The child cannot keep the record. The machine must.