[FAQ] Add: fail-closed admission control FAQ entry#28829
Draft
[FAQ] Add: fail-closed admission control FAQ entry#28829
Conversation
…flows Adds a new Guardrails FAQ entry addressing how agentic workflows behave when an external authority check cannot confirm execution is allowed. Covers on.steps: for pre-agent admission checks, skip-if-match/no-match for query-based gates, manual-approval: for human-in-the-loop gates, and how the safe-outputs/threat-detection layer acts as a backstop. Source issue: github/agentic-workflows#473 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
❌ Smoke Multi PR failed to create multiple PRs. Check the logs. |
Contributor
|
❌ Smoke Project encountered failures. Check the logs for details. |
Contributor
|
📰 DEVELOPING STORY: Smoke Copilot ARM64 reports was cancelled. Our correspondents are investigating the incident... |
Contributor
Contributor
Comment MemoryNote This comment is managed by comment memory.It stores persistent context for this thread in the code block at the top of this comment. |
This was referenced Apr 28, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new entry to the Guardrails section of the FAQ covering fail-closed behavior and admission boundaries in agentic workflows.
What changed
New FAQ entry: "Should agentic workflows fail closed when an external check can't confirm execution is allowed?"
on.steps:,skip-if-match:/skip-if-no-match:, andmanual-approval:curl-based external gate example inon.steps:that fails closed if the service is unreachableSource
Community question in github/agentic-workflows#473 — a broadly reusable design question about where to place admission control boundaries.
Type of change
New FAQ entry (no existing entry covered this topic).