NarrowHighway

A card from a free library — ask anything, no account, works offline. Every card carries its source.

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

concept

A request layer may PROPOSE an action; a separately governed layer admits only a bounded capability; an execution layer may carry out only pre-approved motions; and a reflex layer continuously limits the physical envelope — 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 controlled machine, 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.

source
a robotics control architecture — Matt Harris · a robotics control architecture
card id
card_doctrine_authority_chain
address
SCI.doctrine.EXP/a-request-is-not-an-authority-the-four-layer-cha/REF.WITNESSED@a-robotics-control-archi

related in the keeping ↗ · raw JSON ↗

adjoining cards

Is this card incomplete? Tell the library — it will call out for more ↗