A physical endpoint is a paste, not a robot login

The next Grok Bot shelf is a body in the room.

That job is still a snapshot. Pose, battery, a caption the operator wrote, a tote count they already took. It is not a pairing pin, a lock code, or the robot maker's cloud.

The brick order

1. Physical foundation — ENDPOINT.md, ZONE.md, MOVE.md.
2. The loop — PLAN.md, then a yes, then LOG.md from what actually moved.
3. One first-name role — KEEL on the floor, STOOP at the door, LOCKET on the tote, HALLWARD in one room, NIGHTSHIFT after hours, REX on the bench.

Clerk and Scout can stay on the same computer. They do not drive.

What this shelf will not do

Invent an OEM API. Watch a neighbor. Open a locked door. Store a garage code in markdown. Identify a stranger. Fire a tool. Pay anyone.

RED in the plan means stop. A person in the path caption is RED. Low battery is RED. An unmarked cell is out.

Grok Bot setups stay free so the agent on the shared computer can fetch the page.

Official overview: https://docs.x.ai/grok-bot/overview