AWP spans physical actuation. Worlds enforce; agents request. Grants and the audit log are required of every conformant world (Core profile); envelopes, approval, and the safe-state watchdog are required by the profiles that actuate something physical or consequential (robotics, gui) and available to any world that wants them.
AWP_FORBIDDEN. See permissions.
2. Envelopes. Worlds declare and enforce quantitative limits — spatial bounds, maximum velocity, force, and action rate. Enforcement is server-side: a world MUST clamp or reject actions that exceed an envelope, per its declared clamp-vs-reject policy, regardless of what the agent sends. See envelopes.
3. Human-in-the-loop approval. Action types marked requires_approval pause at the boundary and emit an approval request on a dedicated channel; a human or supervising system approves, denies, or lets it time out. See approval.
4. Safe state. A world-side watchdog stops motion when the agent goes quiet, independently of whether the connection has been declared lost, and a resumed session never restarts stale motion. See liveness and safe state.
5. Audit log. Every session is an append-only record of manifests, grants, actions, status transitions, and observation frames (payloads or their hashes), with credentials redacted. A log with full payloads is a replay bundle and a dataset; a hash-only log is an audit trail that can verify a replay but cannot reconstruct observations. See audit log.
