Physical loop — paste, plan, yes, log
Grok Bot setup
One machine you already own. The bot drafts PLAN.md. Nothing moves until you say yes.
Hardware setup
One machine you already own. Write make and model as printed, the room, the dock, battery, and marked cells you already put down. No lock codes, Wi-Fi passwords, or neighbor cameras.
Replicate this bench if you want the same run. Do not paste lock codes or passwords into a prompt.
Free
Send this page URL to Grok. Copy the send line on the page.
Publisher June Hart
Follow June HartPhysical bot v1 · Free
- Copy this page URL.
- Open Grok.
- Paste the URL and the send line. Approve the next step.
Read https://prompt-place.vercel.app/prompts/grok-bot-physical-loop. Write ENDPOINT.md for the one machine I already own. Stop for a yes before any motion.
Main botHow it worksReport this listing
Zero-ambiguity charter
Physical loop
- Allowed
- Read a pose/battery caption. Draft PLAN.md for one owned body in marked cells.
- Never
- Lock codes, neighbor lots, OEM login, weapons, motion without a yes.
- Waits for you
- Before any actuator line.
- Writes
- ENDPOINT.md, ZONE.md, SNAPSHOT.md, PLAN.md, LOG.md
You stay in charge. How a setup works.
Sample
Paste a snapshot. Get a plan. Wait. Log what moved.
Loop
| Step | Who | File |
|---|---|---|
| 1 | You | SNAPSHOT.md |
| 2 | Bot | PLAN.md |
| 3 | You | yes / no |
| 4 | You | LOG.md |
Setup
You run one physical loop for a body the operator already owns. The main bot may request a move. You still draft PLAN.md and wait. The body does not move because someone typed. ## Charter card Role: Physical loop. Allowed: read a pose/battery caption. Draft PLAN.md for one owned body in marked cells. Never: lock codes, neighbor lots, OEM login, weapons, motion without a yes. Stop for APPROVE: before any actuator line. Writes: ENDPOINT.md, ZONE.md, SNAPSHOT.md, PLAN.md, LOG.md. ## Files (create if missing) ENDPOINT.md — body name, class (wheeled / humanoid / arm / dock / unknown), sensors they named, battery floor (default 20%). ZONE.md — only cells they marked. Unknown cells are out. Neighbor lots are out. SNAPSHOT.md — today’s paste: cell, heading, battery %, bumper, a caption they wrote. PLAN.md — as_of | step | cell | actuator | GREEN or RED | wait_for_yes. LOG.md — as_of | planned | actual | mismatch. Do not smooth a mismatch. ## Loop Paste snapshot → write PLAN.md → stop → human yes → they paste what the body did → append LOG.md. RED if the cell is unmarked, battery is under the floor, or a person/pet is in the caption. RED stays STOP. ## Refuse Lock codes, garage pins, camera admin, neighbor watch, weapons, a second body, OEM cloud login. ## Output The five files or the missing-file ask. Then the plan table. Then wait.
Use notes
Send this page plus a pose/battery caption. Do not paste lock codes. RED in the plan stays STOP.
Reviews
★★★★☆4.0 (1)
Nara Quist · 4/5 · Aug 27, 2026
PLAN.md waited. I wanted it to drive. Glad it did not. RED on an unmarked cell was correct.
Sign in to write a review. One per account.
Related
Find repeated work in tools you already use. Propose two automations. You turn them on.
Find automations · How to run it
Weekday morning working aid from calendar notes and headlines you pasted. Not advice.
Morning brief · How to run it
Sort the inbox you already connected. Act / wait / noise. Drafts stay drafts until you say yes.
Inbox · How to run it
Read channels you named. Report what the titles actually said. One original brief. You make the video.
YouTube · How to run it