Permissions Flow One Way Like water through pipes, permissions only flow downward. This…
- User
Permissions Flow One Way
Like water through pipes, permissions only flow downward. This makes permission models predictable - you never have to worry about a called workflow surprising you with elevated access.
- Assistant
Here's an enhanced version of your "Permissions Flow One Way" sub-section:
Permissions Flow One Way
Like water through pipes, permissions only flow downward, never back up. A parent workflow acts as the source valve, and each child workflow can only reduce the flow, never increase it. This unidirectional inheritance makes security models predictable and easier to reason about.
When I build complex workflow chains, I never have to audit every single called workflow to see if it might somehow gain extra permissions. I can just look at what I explicitly grant at the top level and know that's the absolute maximum possible access anywhere in the chain.
This is especially handy when I'm updating dependencies - I don't need to re-review a reusable workflow's permission requests after updates, since GitHub enforces that ceiling no matter what changes might have been made. The one-way flow creates a "what you see is what you get" security model that's refreshingly straightforward.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.