With workflows running as their declared identity (archie-core-zfv0), every attempt re-checks run for the invoker and the declared identity. The binding invocation check at capture time carries the event's signature result and address, but the run-time re-check has no event context. A Cedar policy that permits run only for a verified signature passes at dispatch and is refused when the task runs, parking every such binding task. Carry the capture's signature context on the task (or record the dispatch decision) so the run-time check evaluates the same facts. Done when a signature-conditioned policy that admits a binding also admits its task at run time, and an unsigned event is still refused.
Close reason
Closed
Imported from beads archie-core-bmro8 · GitHub #1609 · type bug · priority P1 · created 2026-10-11 · closed 2026-10-13
With workflows running as their declared identity (archie-core-zfv0), every attempt re-checks run for the invoker and the declared identity. The binding invocation check at capture time carries the event's signature result and address, but the run-time re-check has no event context. A Cedar policy that permits run only for a verified signature passes at dispatch and is refused when the task runs, parking every such binding task. Carry the capture's signature context on the task (or record the dispatch decision) so the run-time check evaluates the same facts. Done when a signature-conditioned policy that admits a binding also admits its task at run time, and an unsigned event is still refused.
### Close reason
Closed
---
_Imported from beads `archie-core-bmro8` · GitHub #1609 · type bug · priority P1 · created 2026-10-11 · closed 2026-10-13_
sam
added the highbug labels 2026-10-27 13:39:37 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
With workflows running as their declared identity (archie-core-zfv0), every attempt re-checks run for the invoker and the declared identity. The binding invocation check at capture time carries the event's signature result and address, but the run-time re-check has no event context. A Cedar policy that permits run only for a verified signature passes at dispatch and is refused when the task runs, parking every such binding task. Carry the capture's signature context on the task (or record the dispatch decision) so the run-time check evaluates the same facts. Done when a signature-conditioned policy that admits a binding also admits its task at run time, and an unsigned event is still refused.
Close reason
Closed
Imported from beads
archie-core-bmro8· GitHub #1609 · type bug · priority P1 · created 2026-10-11 · closed 2026-10-13