blueclaw
Boundaries

Capability authorization

Capability authorization is the per-person check on which capability operations a requester may invoke.

POSIX decides what a process may touch on this machine. It cannot decide whether a person may send a message as the company or change a shared calendar, because those effects happen in the capability service with that service's authority. internal/access (CanAccess) is consulted before capability and record catalog tools are exposed, and it is the only per-person authorization on those operations. It sits in front of the service's socket; moving the decision into the service that performs the effect is open work.

What is not enforced

blueclaw has no executable allowlist, no denied command list, no denied path prefix, and no prompt instruction telling the model what it may not touch.

Known gaps

These are the places where the boundary above does not hold as stated.