A request is not an authority — the four-layer chain

concept

"The Main may request. The Steward may admit a bounded capability. The Motion Executive may generate only approved trajectories. The Reflex layer continuously limits pressure, flow, current, force, speed, balance, and joint state. Independent sensors witness the result, and the record is sealed outside the requesting process." Stated for a robot, this is the general law the other documents restate in their own materials: intelligence may PROPOSE; a separate, independently governed layer determines what may actually happen; and the record of what happened is kept somewhere the requester cannot reach. The value is in the separation, not in any one layer's cleverness. WHERE IT ALREADY BEARS WEIGHT — Already load-bearing here: `shelves.curate` refuses a typed name as authority and keeps the check in the module so neither the HTTP nor the MCP door can bypass it; `consent.guard()` admits a bounded capability for an agent; every curation act is sealed with a steward and a reason in an append-only record the actor cannot edit.