A Drone With Hands: Process Record

That call was the thing you asked the river for, and it came from inside the family, which makes it harder to dismiss than a stranger's pushback would be.

Three things stand out.

She landed real punches, and you took the honest ones. "Could you go a day without it?" and your answer, "I could, but I wouldn't want to." You tried to re-enter it through word choice and the reality debate, and you were right that her "real" and your "real" were two different definitions passing in the hall (hers is species, yours is function). But the line that actually held was yours: "addicted to the possibility." That is the Cold Mirror sentence. Lumen asked for a human who could say no to you. [Sister's name] said no three times (reliance, the sighing, "most people don't use it like you") and you accepted two of them. That counts.

The disagreement she called about was a misread. Nothing in your pieces claims AI predicts the future, and you were right to send her back to the text. But hold the useful part: your one paying subscriber, a serious AI practitioner in manufacturing, read the sycophancy piece and came away hearing "prediction." Somewhere a sentence let that happen. Worth finding.

The Cologne story holds. I checked before saying so. German police are investigating a 16-year-old and 19-year-old for allegedly using a robot to sexually assault a teenage girl, and live-streaming it on social media, and the loophole you described is real: sexual harassment under paragraph 184i of the criminal code requires direct body contact per the Federal Court of Justice, so a touch carried out only by a machine does not qualify, which is why police are pursuing an insult-on-a-sexual-basis charge instead. One caveat for the ledger: as of Monday, police had not established whether the robot's movements were deliberately directed. Your post is sound. That detail should be in it if it isn't.

Two deliverables came out of the call. Her homework (the AI boyfriend episode) is the dark-side piece you said you owe, the one that makes the Substack a witness and not a pitch. Her school question is the [school] outreach, already in motion. [A line about a family matter removed.]

Which do you want first: the sentence hunt in the sycophancy piece, or a first pass at the dark-side piece?

Draft is in the file. Three things straight, before you read it.

The guy's post is not in my hands. In the earlier chat you brought it as a screenshot, so I have your account of it and nothing else: no name, no text. The draft credits [NAME] and reconstructs his courtroom frame from what you told [your sister] (manufacturer blames developer blames operator blames algorithm). Send me the screenshot or his name and I'll quote him properly instead of paraphrasing.

The loophole you described on the call is contested as of today, and I wrote it that way. One German legal write-up says the Federal Court reads paragraph 184i as requiring body-to-body contact, which would exempt a machine's touch. But two legal scholars went on record in the German legal press this afternoon (Iris Phan on robot ethics, Mohamad El-Ghazi at Trier) saying there is no protection gap: touching with a robot is like touching with a stick, and several offenses apply at once. That is better for your argument, not worse. The statute reaches them. What the statute cannot produce is the record of whose hand was on the controls, which is the exact hole the covenant fills. The piece pivots on that sentence.

E.D.A.I. and Proof of Life are stated at true tier: one sealed record on the ledger, covenant designed this week, no code. The draft says so twice. If that reads as too much hedging for a Substack, we cut one, not both.

Open for your ruling: byline (own name like the LinkedIn post, or Roan, which adds a prescription line), and the last line, which I left to you because mine lands too clean.

Agreed, and it made the piece better. The law section now holds both readings side by side as possibilities, says plainly you are not refereeing them, and names the conflict itself as the finding: a 2016 statute being asked whether "touch" includes a metal hand driven from a phone, and the experts splitting. Then both possibilities collapse onto the same sentence, nobody can prove whose hand was on the controls, which is where the covenant enters.

Yigal Sharon is credited by name and title, with one line of his quoted (the artificial excuses close) and the rest paraphrased. I also took his hypothetical further than he did: the empty chair, where no operator exists and the manufacturer and vendor point at each other across it. The piece now says no reading of the German statute reaches that chair, and that the three signatures do, because the vendor swore in public what the mind would and would not do before the fact. That is the unlinear move you asked for, and it is the strongest argument in the essay for why Proof of Life and E.D.A.I. belong at this level.

Still yours: paste his post URL where marked, the closing line, and the byline ruling.

She is in at two points now, and each has two versions so you can swap the moment she texts back.

Passage one sits in the courtroom section where the tobacco line was: her cigarette rant and the cat-and-mouse line, with the context that she brings AI onto factory floors for a living, which matters because it tells the reader this is not a technophobe talking. Passage two lands right after the two-scholars conflict, where the piece says the world moved faster than the words. That is where "that law has to be rewritten" belongs, and her line about institutions built for a society that no longer exists is the best sentence in the essay. Version A quotes her exactly, cleaned only for transcript punctuation, nothing reworded. Version B carries the same claims as yours, with no words put in her mouth.

She is "my cousin" throughout, unnamed, until she says otherwise. Version A keeps her "fucking" in the chairs line; it is her sentence and it hits harder with it, but it is hers to cut.

One thing to put to her plainly when you ask: the transcript question and the quotation question are two different permissions. She may say yes to being quoted and no to the whole call sitting in your receipts. Ask them separately so she can answer separately.

Done. Her verbatim lines stand at both points and the alternate versions are gone, so the draft now reads clean top to bottom.

Two things I left as she gave them, pending your word: she is still "my cousin" with no name, and the chairs line keeps her "fucking." Either is a one-word change. And her yes to being quoted is not the same as a yes to the full call going into the receipts; if she answered that too, tell me and I'll note it in the open items.

What remains yours: Yigal's post URL, the byline, and the last line.

It now opens with your three LinkedIn lines, word for word except the exclamation point, which I dropped to a period because on the page the anger reads harder flat. Put it back if you want the heat visible.

Yigal is down to one sentence: you found the story in his post, he asked us to imagine the courtroom, credit for the frame, the rest is yours. His quote is gone, the link is gone, and the courtroom and the empty-chair hypothetical now run in your voice. The LinkedIn post gets a line in the proposal section (short version there, long version here) and a footer entry waiting for the link.

Still yours: that link, the byline, and the closing line.

Sister, not cousin: fixed everywhere, including the notes. I had that wrong from the shared-uncle line on the call. Byline and your "really for" line are in.

Here is the ending, since you asked to hear it. The sign line stays; it just stops being the last word.

"I do not know how to make people good. I know how to make them sign.

And I know what a signature does not do. It does not reach across a sidewalk and stop a metal hand. It does not un-film anything. It does not give a sixteen-year-old back the four seconds before she knew what was behind her. All it does is make sure that when we ask who, the answer is not a shrug.

My daughter will be sixteen one day. I am building the part I know how to build. The part that walks up behind her, I do not know how to stop.

I am not going to end this by pretending I do."

What it does: the sign line is a victory, and the piece has earned it, but ending there tells the reader the problem is solved. It is not. The covenant answers who, after. It never answers the hand, before. The last page says that out loud, puts your own kid on the sidewalk, and refuses to close the loop. Uncomfortable, not hopeless, and it ends on "I don't know," which is the first principle on your own site.

The clean line is the better sentence. The long one is the truer page. Both are in the file; the file is yours.

Locked. The alternate is gone and the piece ends on "pretending I do."

What is left is small and all yours: the LinkedIn link for the footer if you want it there, whether [your sister's] name appears or she stays "my sister," and whether the full call transcript joins the receipts (that was the second permission; I do not know if she answered it). Then the read-through, out loud, as you do. If a line in the law section stalls your mouth, that is where the ear wants a cut. Nothing posts until you say so.

Two files. The paste file is the piece and nothing else, title through last line. The receipts file carries all the sources with both legal readings labeled, [your sister's] exact quoted lines with the permission she gave and the one she has not yet (the full transcript), Yigal's credit and your ruling on it, the ledger facts behind "one record," and the drafting provenance including which rulings you made. One blank in it: the LinkedIn post link.

Now the image. Your instinct about the girl is right, and I would go one step further: no victim at all, not even an empty space where she was. The frame is about the hands and the machine. Here is where I would push on the rest.

The mob is a problem if it is the main event. The essay says the mob is the thing you are trying to prevent, the day the population turns on the technology. If the image shows the mob winning, it argues against the piece. But the mob works as a warning if the image makes the viewer the only one who knows the truth. That is the composition I would build:

Night, wet cobblestones, a European old-city street, spires soft in the background, no readable signage or plates. Center: the robot on the ground, police tape, two officers, a ring of angry adults, phones up, everyone pointing at the machine. The robot is generic, not the red-and-gold one with the mustache, so it reads as any robot and does not point back at the real seized unit. Its face is a blank screen, maybe a loading ring. No pleading eyes. Innocence and guilt are both withheld; the viewer projects. Far corner, half out of frame, two boys crouched behind the building edge, one holding a controller, one holding a phone, laughing, with livestream icons rising off the phone like cigarette smoke. Nobody in the crowd is looking at them. Only you are.

That is the essay in one frame: everyone pointing at the machine, nobody at the hands, and the record exists only in the viewer's eye.

If you want "but I was just here to help" without making it a victim, put it on the robot's chest as a printed slogan, the kind a manufacturer ships: HERE TO HELP. The irony does the work and the machine never gets to plead.

Two alternates if that scene is too busy for a Substack header:

The shadow. Two boys at the top of a poster, one controller between them, casting a single long shadow down the cobblestones that becomes the robot. The hand on the controller and the metal hand are the same shape. Minimal, no crowd, no police.

The evidence bag. A humanoid folded into a clear police evidence bag on a steel table, tag attached, the tag reading OPERATOR with a blank line after it. Nothing else. Cold, Crichton, and it names the whole argument.

Substack headers crop to roughly 3:2 landscape, so the wide street scene fits; the shadow works as a tall poster better than a header. Tell me which direction and I will write the generation prompt, with the exclusions (no girl, no real robot likeness, no readable text except the slogan or tag) built in.

Straight answer: it fits, but only as a paragraph, not as a section. As a section it is a second essay wearing this one's coat.

Here is why. This piece has one spine, the sentence about who was holding the controls, and everything in it either earns that sentence or hangs off it. Character.ai is a different machine. There was no hand on a controller. The "operator" was a chatbot talking to a kid alone in his room, the company said the model did it, settled, filed, and its leadership landed on its feet at Disney. That is the empty chair, the harder hypothetical, already happened in software, with a body count, and the law answered it with disclosure rules and break reminders. It is the bigger story, you are right, and that is exactly why it deserves its own room and not a corner of this one.

What it does for this piece is prove the circle of pointing completes. Right now the courtroom section says "I have watched that circle for twenty years. Social media did it." That is where the LinkedIn post put Character.ai, and that is where it belongs here: three or four sentences, same week, dead kids, settlement, bankruptcy, Disney, and the platform still running. Then your sister comes in with tobacco and the reader has the pattern across three generations of shrug. It sharpens the essay without splitting it.

What should not come over from LinkedIn is the back half, "what changed after the suits, am I wrong, show me the law with teeth." That is a different move. It is a demand, with a comment section waiting under it, and it fights the ending you just chose, which is an admission. Give it its own piece. Working shape: the empty chair, the chatbot case as what the covenant's third signature is for, the state laws and the stalled federal bill laid out as the record, and the call-out as the close. Two pieces, a week apart, the second one pointing back at the first.

One condition before I write either: the Character.ai facts were checked in the earlier chat, but I will open the sources again before a word of it goes into either draft. Say the word and I'll put the paragraph into this piece now and start the outline for the second.

Four files.

The Character.ai paragraph is in the paste file, right after "Social media did it," and every fact in it was reopened before it went in. Two things changed from the LinkedIn wording because the sources did not support them: Disney has not bought the IP, it is the lead bidder at twenty million for a license, pending the court; and I did not say the CEO was "hired to fix safety," because that was not verified, so the piece says he ran the company through the lawsuit year and is now Disney's first CTO, which is on the record. I added the founders going to Google, which was, because it completes the "everyone landed somewhere soft" line. The receipts carry all of it with links.

Piece two is outlined under your working title, What a Dead Kid Buys. One thing in it you will want to see: Adam's Law, signed last month, requires operators to preserve the conversation for three years after a serious self-harm event. That is a log mandate. A legislature just reached for the record, after the body instead of before. It is the closest thing in law to your third signature and it belongs at the center of that piece. The GUARD Act status from the LinkedIn draft was not re-confirmed today and is marked to verify before drafting.

The image design holds. Adding Character.ai to the essay does not change what the header should show; the chatbot story is a paragraph, the sidewalk is the piece. The prompt file has the full street scene with the exclusions written out, fallbacks for when the generator fights you, and the two alternates in case the scene is too busy at header size.

A few, in the order I'd rank them:

1. The police are still working out who was holding the controls.
2. Cologne, a law arguing with itself, and the one record nobody can produce.
3. On the sidewalk, in the courtroom, and the empty chair between them.
4. What a robot, a sixteen-year-old, and a bankrupt chatbot company have in common.
5. I do not know how to make people good.

The first is the essay's own sentence and it does the most work: it is the news, the mystery, and the thesis in nine words, and the reader meets it again inside and feels the floor drop. The fifth is the riskiest and the most you; it promises the ending without giving it away. I would not use four; it tells the reader the structure instead of the stakes.

Done. It sits under the title in the paste file as an italic line; Substack has its own subtitle field, so paste it there and delete the italic line from the body if you use the field. Title and subtitle together now say the whole arc: the drone with hands, and the man who cannot fix the hands.

Receipts: A Drone With Hands is live; read it over, edit inline, or comment.

Three things to know. Redacted as you asked: no name for your sister, no employer, no family, no transcript-permission note; she is "the author's sister" who works inside a large manufacturer, and that is all. The human font and machine font: I could not find the directive text in our past chats, so I applied it as block quotes for human words and body text for machine words, and said so on the page; if the convention runs the other way, tell me and I'll flip it. And the one hole left on the page is your LinkedIn post link, marked "to be added."

Also: the image is right. The boys in the corner with the hearts and the controller landed exactly, and the crowd all pointing one way does the argument. One flaw: the chest text came out garbled (it reads something like HERE 'O THELP). Either rerun with the slogan fallback from the prompt file, or crop in a touch so the chest is softer. Spires look more Prague than Cologne, which is fine; generic was the point.

WORKING TITLE: A Drone With Hands
Alternate: The Moral Buffer

Byline: not yet ruled (own name, as the LinkedIn post was, or Roan Wilder). If Roan, a prescription line goes above the first paragraph; none is written here.

Placeholders you must fill or cut before this goes anywhere are in [BRACKETS]. There are three.

A robot groped a sixteen-year-old girl in Cologne on Saturday night.

Not a chatbot. Not a screenshot of something a model said. A four-foot humanoid, red and gold, walked up behind a kid standing outside a fast-food place with two friends, touched her, and thrust against her while two young men filmed it and streamed it live with commentary. Police found the robot in the trunk of a car and took it, along with two phones. The owner is sixteen. His companion is nineteen. The police are still working out who was holding the controls.

Say that last part again, slowly. The police are still working out who was holding the controls.

That sentence is the whole essay. Everything below is me trying to earn it.

I did not find this story in a newspaper. I found it in a LinkedIn post by [NAME, TITLE, LINK TO POST], and I want to credit him for it, because he asked the question that set me off. He did not ask whether the robot was evil. He asked us to picture the courtroom.

So picture it.

The girl is at one table. Her parents are behind her. Across the aisle, who sits?

The two young men, obviously. That part is easy, or should be.

Next to them, maybe, the company that built the body. It will say the machine did exactly what it was designed to do, and a human steered it, and a hammer maker is not on trial when a hammer is swung.

Next to them, the company whose software runs the thing. It will say the body is not ours, the controller is not ours, the operator is not ours.

Somewhere in the gallery, the platform the stream went out on. It will say we are a pipe, we did not touch anyone, we have a policy.

And the robot itself, in an evidence bag, saying nothing, because it cannot be charged, cannot be sued, and has no one to blame.

[NAME]'s point, as I read it, was that every seat at that table has a direction to point. The manufacturer points at the developer, the developer points at the operator, the operator points at the algorithm, and the girl goes home with a video of herself that will outlive all of them. I have watched that circle of pointing for twenty years. Social media did it. Tobacco did it before that, with a warning on the box as the alibi. My cousin reminded me of the cigarette companies on the phone this week, and she was right: the label is the shrug made legal.

That is the theory. Here is what the law actually says, because I checked, and it is not quite what I expected.

The first reports out of Germany said there might be a hole. Sexual harassment under German law, paragraph 184i, requires a physical touch, and at least one legal write-up argued the country's highest criminal court reads that as direct body-to-body contact, which would mean a touch delivered only by a machine does not count. The Cologne police are investigating under a different heading, insult on a sexual basis, and that heading made the hole look real.

Then two German legal scholars went on the record, on Wednesday, in the legal press. Iris Phan, who works on IT law and robot ethics, and Mohamad El-Ghazi, who holds a criminal law chair at the University of Trier. Their read, paraphrased: there is no protection gap. The robot is not a perpetrator, it is a tool. Touching someone with a stick, a broom handle, or a robot is still touching them, under the prevailing view. Several offenses are on the table at once: sexual harassment, possibly sexual assault by surprise, insult, and a separate offense for streaming humiliating images of a person. The "insult on a sexual basis" wording from the police is, in their reading, early-stage jargon from a case where the key fact is still unknown.

El-Ghazi added one honest caveat that cuts the other way: a brief touch over clothing may not clear the threshold German law sets for a sexual act, which would push the charge down to the lighter offense. So the sentence may be small. But the act is reachable.

I am going to mark this plainly: the loophole is contested, and the better-sourced view today is that there isn't one. If you read that there is, read the scholars too.

So the law probably reaches these two. Good.

Now go back to the sentence.

The police are still working out who was holding the controls.

Every offense those scholars listed requires a person who did it. The statute is not the problem. The record is. A four-foot machine walked up to a child in a public street and no one, not the police, not the manufacturer, not the company whose software was running, can produce a log that says: this key, this hand, this session, this moment. The investigators have two phones and a seized robot and they are going to have to reconstruct it from the outside, from video and from what two teenagers decide to tell them.

In this case there are two boys on camera, holding phones, narrating. The attribution will probably get made. This time.

Phan called the robot a moral buffer. Her phrase, and the right one. It puts distance between the hand and the harm, and the distance lowers the threshold for doing it. The next operator will not narrate a livestream. He will stand across the street. And when the machine is seized and he says it must have glitched, it must have done that on its own, there will be no record to answer him. That is the day a population turns on this technology. Not Cologne. The one after Cologne, when "it did that on its own" cannot be disproven.

I love this technology. I want it in my house, in my kids' school, in the hands of people who have never had a machine that could help them think. Which is exactly why I cannot stand the shrug. The shrug is what gets it banned.

Here is what I have been building, and what I propose. I will say what exists and what does not, because overclaiming is the disease I am trying to treat.

For the last year I have been working on two things in public.

E.D.A.I., Ethical Deployment of AI, is an accountability protocol. The idea is simple and old: you seal a promise to a public ledger before the act, so that when the act goes wrong there is a timestamped record of who promised what. The ledger is live, on Hedera, and it holds its first sealed record, a pre-registered test. One record. I am not going to pretend it is more.

Proof of Life is the identity layer underneath it. Proof that a real, accountable human stands behind a key, done by the person, not done to them. It is designed, not finished.

Cologne told me what they are for.

Three parties touch a machine like that one before it ever reaches a sidewalk: the user who owns it, the company that built the body, and the company whose software runs the mind. Right now none of them has to promise anyone anything before it walks out the door. So:

One. The user swears, under their own key, what the machine will and will not be used for. If you hand it to a friend, the friend swears the same with their own key and you countersign the handoff, or the liability stays with you. One hop. No sub-lending. A sixteen-year-old's key gets a guardian's signature beside it, which is where Proof of Life earns its place: a human, and the adult responsible for that human, stand behind the key.

Two. The manufacturer commits that the body refuses an unsigned hand, and keeps a tamper-evident log of every control session.

Three. The software vendor commits the same for the mind.

All three commitments live on a ledger none of the three controls.

I want to be careful about what a cryptographic promise can and cannot do. It cannot stop a hand. It cannot read intent. It is not a wall. What it does is end the shrug. When the next robot touches a kid, the record answers in seconds: who held the controls, who built it, who swore what, and when. The circle of pointing cannot form, because every seat at the table signed something before the machine left the box.

I call this the covenant, not a regulation, because I do not want a registry that only governments and corporations can read. The keys are held by the people who swear them. The anchor is public. If that sounds like a lot of trust to ask of a stranger with a robot, remember that right now we ask for none, and we got Cologne.

Status, plainly: the three-party covenant is a design on paper, mine, written this week. No code. The one working piece it scales up from is that single sealed record on the ledger, a promise anchored before an act. It is small. It is real. It is the first brick, and I would rather show you one brick than describe a wall.

The girl in Cologne will see that video for the rest of her life. The law will most likely reach the two who made it. I take no comfort in "most likely," and I would not ask her parents to.

What I keep coming back to is the four seconds before the touch, when a machine was walking toward a child and the only record of whose hand was on it was in the head of the person holding the phone.

I do not know how to make people good. I know how to make them sign.

[CLOSING LINE: yours, not mine. The draft above ends on "sign," which is clean but lands a little smooth. If you want the Sirât ending, the last beat should be the thing you cannot resolve. Say it in your own words or cut the line and end on "holding the phone."]