gate-keeper

Require two independent proxy assessments before issuing sprint gate approval tokens.

9|Updated Apr 2, 2026

Search Tags:#consensus #evidence #policy #approval #sprint #proxy #gate

Ready to run

npx skills add https://github.com/dazzaji/interlateral_agents --skill gate-keeper-dazzaji

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gate-keeper
Source: https://github.com/dazzaji/interlateral_agents/tree/main/.codex/skills/gate-keeper
Command: npx skills add https://github.com/dazzaji/interlateral_agents --skill gate-keeper-dazzaji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Two independent agents must approve sprint gates to prevent unilateral risky changes, ensuring adherence to delegation and human-facing policy before execution.

Core Features & Use Cases

Independent proxy assessments ensure checks and balances for gate decisions
Enforced consensus before issuing an approval token or denial
Strict adherence to delegation authority, policy, and evidence requirements
Use Case: when sprint gates (deploy, live mutation, push, cleanup, skip, or short-watch) require dual-human-like judgment

Quick Start

Submit a gate request packet and await two independent proxy assessments to obtain a consensus-approved gate token.

Frequently Asked Questions about gate-keeper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce dual independent approvals for sprint gate decisions like deploy or push?▼

Dual proxy gate approvals require two independent agents to assess delegation authority, policy adherence, and evidence before authorizing sprint gate actions such as deploy, push, or cleanup. This prevents unilateral risky changes by enforcing mandatory consensus.

What is a consensus-based proxy approval council for sprint gates?▼

A consensus-based proxy approval council is a two-agent system that independently evaluates gate requests against delegation authority and human-facing policy. Both proxies must concur before a scoped, verifiable approval or denial token is issued for actions like live mutations or shortened watches.

How do I require evidence and artifact checks before authorizing a live mutation gate?▼

Evidence and artifact checks are enforced by submitting a gate request packet that two independent proxies evaluate. Each proxy verifies strict policy adherence and delegation authority before concurring, ensuring no live mutation or cleanup gate is authorized without verifiable evidence.

When do I need dual-proxy consensus for sprint gate approvals?▼

Dual-proxy consensus is needed when sprint gates such as deploy, live mutation, push, cleanup, skip, or short-watch require two independent human-like judgments to prevent unilateral risky changes and ensure strict adherence to delegation authority and policy.

Can I use a single proxy to approve sprint gates instead of requiring two independent assessments?▼

A single proxy cannot approve sprint gates under this approach. The system mandates two independent proxy assessments to produce checks and balances, ensuring enforced consensus before issuing any approval or denial token for gate decisions.

What are the limitations of using a dual-proxy gate approval system for sprint gates?▼

The dual-proxy gate approval system requires mandatory delegation authority, independent assessments, and strict policy adherence for every gate decision. It cannot issue unilateral approvals, meaning skip, deploy, or cleanup actions will be denied if both proxies fail to concur.