Hacker NewsBuilt this around one simple idea:
the workflow that wants to execute should not be the same place that decides whether execution may continue.
This project puts an external allow/deny boundary before action.
Public entry points:
* live pilot * commercial request * private deployment
There is also a GitHub Marketplace action install surface, but the main point is the boundary model itself: decision stays outside the workflow that is asking to proceed.
Looking for feedback from people working on CI/CD, security controls, approval boundaries, and automated execution.
loading...