Permissions
Someone who can inspect a market observation may still lack permission to delete it.
Follow those two operations through the Scavenger controller.
Reading requires altar:read. Deletion requires runs:cancel and a current decision about
this actor and observation. The controller tests
include revocation during a read and a separate denial at deletion.
For a new action, name the actor, resource, and effect. Apply the scope guard to the authenticated caller's Sigil. Have the owning service check current authority on the exact operation, including after a wait. Exercise both admission and refusal. The credential authenticates the caller. The Sigil carries bounded claims without that secret.
Add application actions in Core. The extension context has no permission store. IAM owns grants and revocation. If the action also changes the host, follow Privileges for the additional effect boundary.