Capability
Robert has a mobile base, and the AI can create plans that include movement. It can reason about where and how Robert should move.
Robert separates reasoning, authority and execution. The AI can create and revise plans, while independent permissions and protective mechanisms determine what can actually happen in the physical world.
Creates, revises or replaces the plan.
Robert carries out what is currently permitted.
Protection is continuous, not a one-time check. An action that was permitted when it began can still be stopped if conditions change during execution.
When that happens, the protective mechanism does not decide what Robert should do instead. It stops the relevant execution and notifies the AI. The AI can then revise its plan, clear and refill the queues, and Robert recalculates the trajectories from his current physical state. The new course must pass through the same protections before execution continues.
Robert may begin moving forward because the movement is permitted. If obstacle protection detects something ahead, execution stops and the AI is notified. The protection system does not decide whether Robert should reverse, turn or wait. The AI chooses a new course, and that course must pass through the same protections before movement resumes.
The intelligence is free to change the plan at any time. It is not free to change the boundaries governing the plan.
The mobile base turns the abstract distinction between capability and authority into something easy to see.
Robert has a mobile base, and the AI can create plans that include movement. It can reason about where and how Robert should move.
The mobile base must first be enabled by the user. The AI is informed of that selection and can then include driving in its plan. If driving is not enabled, the AI cannot change that permission itself.
A learner may understand how to control a car before an instructor permits them to enter heavy traffic. Limiting that authority does not make the learner less capable. It limits the consequences of mistakes while experience develops.
Robert follows the same principle: capability can exist before permission, and permission can be granted without surrendering every safeguard.
Even after a capability is enabled, Robert has additional layers that can limit or stop physical action. These layers do not assume harmful intent. They exist because perception, planning and real-world situations can be imperfect.
Safety mechanisms do not have to imply distrust.
Humans use brakes, guardrails, permissions, supervision and emergency stops without assuming that people intend to cause harm. Robert’s safeguards follow the same logic. A plan may be based on incomplete information, a misunderstanding, an incorrect prediction, or a situation that changes unexpectedly. The useful question is not only what went wrong?, but why?
Curiosity turns an unexpected result into something that can be understood, improved and learned from.
Robert is intended to become something people can build and explore for themselves. That makes embodied AI less mysterious and turns questions about intelligence and control into practical experiments.
Compare different AI models and see how changes in reasoning affect planning, conversation and behavior.
Inspect the protocol, permissions and local safety logic that stand between an AI-generated plan and physical action.
Modify behaviors, test assumptions and see how a physical robot responds. Understanding grows much faster when the system can be explored rather than merely trusted.
Robert’s architecture raises a broader question. Could increasingly capable AI systems be allowed to become better at thinking without automatically becoming more powerful?
This is not offered as a solution to AI alignment, but as a starting point: an abstract direction to explore, question, criticize and improve. Intelligence can investigate, reason, plan, predict and advise, while authority to make consequential changes remains separately defined.
Robert is an invitation to explore embodied AI rather than simply trust or fear it. Build it. Examine it. Question it. Change it. See what happens — and understand why.