feat(signing-gate): verdict → signing-gate compose seam - #262
Merged
Conversation
A generic, fail-closed adapter a downstream custody/signing layer plugs into: given Gecko's anti-poisoning SafetyVerdict, decide whether to sign/release a credential for a tool. Gecko detects at comprehension time; the signer enforces. Gecko never holds keys or signs. Proven offline: a poisoned tool is quarantined at comprehension -> gate DENIES; the clean sibling -> ALLOWS; unknown tool -> fail-closed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
What
A small, generic, fail-closed adapter (
gecko/signing_gate.py) that lets a downstream custody / signing layer gate on Gecko's anti-poisoning verdict: refuse to sign or release a credential for a tool Gecko quarantined at comprehension time.This is the verdict → policy proof-of-seam — the concrete artifact behind the custody-partner compose (target partner: a secrets/signing vault for agents). Kept partner-name-generic so any custody/policy engine can consume it.
Why (the compose)
SafetyVerdict, already shipped).How
SigningDecision(allow, tool, reason)— auditable yes/no + why.evaluate(verdict, tool, known_tools=...)— pure function a custody layer calls with a stored verdict (no live surface needed). Fail-closed: unknown tool → deny; quarantined → deny with the sanitizer's reason; clean → allow. Per-tool blast radius (a poisoned sibling never denies a clean tool).gate_surface_tool(surface, tool)— convenience over a liveSurface.Proof (offline, $0, falsifiable)
tests/test_signing_gate.py: comprehend a spec with a clean tool + a poisoned tool →Gate
ruff+mypy geckoclean; targeted suites 14 passed.🤖 Generated with Claude Code