You'll notice
Useful3 Signal3
Artifact actions carrying approval fields nobody issued are denied outright.
What's wrong with this entry?
Anonymous. No account, no email.
What
If an artifact action arrives with internal approval fields that no completed permission check attached to that call, the action is denied and the permission classifier cannot approve it. The denial message points at hooks or SDK hosts injecting the fields. This check always runs.
Evidence
Artifact consent markers not minted by a completed permission check fail closed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.