● PolyLever
● System Online // Gateway.Secure

Autonomous AI Engineering
with Verification Gates

Supervise coding agents with absolute verification gates. Prevent broken commits and unauthorized edits with worktree isolation, automated rollbacks, and an open audit log.

GitHubManual
[ 01 / Gate ]Verification Gate
[ 02 / Isolation ]Worktree Isolation
[ 03 / Control ]Hands-Off Lists
● Installation

Get up and running in minutes

One-line installers for macOS, Linux, and Windows. The installer clones PolyLever, installs bun if needed, and prints next steps. Safe to re-run.

bash installer
curl -fsSL https://raw.githubusercontent.com/lerugray/generalstaff/master/install.sh | bash

After install

1

Run gs welcome for guided setup

2

Register your first project

3

Run one verified cycle end-to-end

Requires git, bash (Git Bash on Windows), bun 1.1+, and an LLM provider (Anthropic, Claude Code, OpenRouter, or Ollama).

● What is PolyLever

AI orchestration
with safety built in

PolyLever treats agentic AI as adversarial input to your codebase. Structure beats better prompts — verification gates, worktree isolation, and open audit logs enforce discipline on every cycle.

Every cycle must pass tests, produce a non-empty diff, and survive independent review before a commit lands.

● How It Works

From bootstrap to verified commit

Every autonomous cycle flows through the same enforced pipeline. The dispatcher orchestrates agents, the verification gate decides outcomes, and failures roll back automatically.

● Step 0101 / 06

Bootstrap Project

Initialize a project configuration with hands-off rules and verification commands via gs welcome.

Pipeline: EnforcedActive Cycle
polylever — setup
$ gs welcome
● Guided Configuration Wizard
→ Project ID: myproject
→ Project Path: C:/code/myproject
→ Verification command: bun test
→ Hands-off files: ["src/safety/*", "CLAUDE.md"]
✓ Configuration written to projects.yaml
● Step 0202 / 06

Assign Task

Queue a work order via session, cycle, or heartbeat inbox — the dispatcher picks up the task.

Pipeline: EnforcedActive Cycle
polylever@terminal: ~/cycles
cycle: #42[RUNNING]
$ gs-agent --live --cycle=42
Initialising agent workspace... done
⠋
Task assignedcycle #42 dispatched to dispatcher
•
Worktree createdpending
•
Engineer executingpending
•
Diff generatedpending
•
Tests passedpending
•
Reviewer approvedpending
•
Safe commitpending
Progress:[░░░░░░░░░░░░░░░░░░░░]0%
pipeline:dispatcher→engineer→verify→commit
● Step 0303 / 06

Engineer Agent Executes

The engineer runs in an isolated worktree, making changes against declared scope only.

Pipeline: EnforcedActive Cycle
git worktree strategy
[MASTER PROTECTED]
master
untouched until merge
bot/work
agent commits land here
.bot-worktree
isolated execution
● Step 0404 / 06

Verification Gate Runs

Tests must pass and the diff must be non-empty. Boolean gates enforced in code, not prompts.

Pipeline: EnforcedActive Cycle
polylever — orchestration
[CYCLE ACTIVE]
Dispatcher
Orchestrator
[ACTIVE]
Engineer
Claude / Aider
[RUNNING]
Reviewer
Isolated AI
[ISOLATED]
Verify Gate
Tests + Scope
[GATING]
bot/work
git branch
PROGRESS
.jsonl audit log
2,052 tests passing
reviewer isolated
BYOK · local-first
● Step 0505 / 06

Reviewer Agent Validates

Independent reviewer confirms scope match and checks every diff against hands-off patterns.

Pipeline: EnforcedActive Cycle
polylever — reviewer
{
"event": "reviewer_verdict",
"cycle_id": "20260417161301_juzs",
"data": {
"verdict": "verified",
"reason": "The diff matches scope...",
"hands_off_violations": []
}
}
● Step 0606 / 06

Commit or Rollback

Verified cycles commit to bot/work. Failures roll back with a full audit trail in PROGRESS.jsonl.

Pipeline: EnforcedActive Cycle
PROGRESS.jsonl — live audit stream
0 events[STREAMING]
waiting for events…
verified
rollback
failure
grep-able · open format
● Documentation

Everything you need to ship safely

From first-run wizard to advanced heartbeat dispatch — comprehensive guides for running autonomous AI workflows with verification discipline.

Local setup (Windows + Claude Code CLI)

Local setup (Windows + Claude Code CLI)

Claude Code as engineer via engineer_command.sh — subscription or API key, one verified cycle with PowerShell transcripts.

Explore
Local setup (Windows + OpenRouter)

Local setup (Windows + OpenRouter)

Install PolyLever, configure OpenRouter, run one verified cycle — every step with PowerShell command and terminal output.

Explore
Getting Started

Getting Started

Run gs welcome for guided setup — provider config, first project, and one verified cycle end-to-end.

Explore
Running Autonomous Cycles

Running Autonomous Cycles

Session budgets, cycle dispatch, and heartbeat inbox mode for 24/7 supervised automation.

Explore
Verification Gates Explained

Verification Gates Explained

The Boolean gate architecture: tests, diff checks, and reviewer verdicts that cannot be bypassed.

Explore
Reviewer Agents

Reviewer Agents

How reviewer isolation catches hands-off violations and scope drift before they reach your branch.

Explore
Worktree Isolation

Worktree Isolation

Bot/work branch strategy, .bot-worktree isolation, and safe merge workflows for your codebase.

Explore
Audit Logging

Audit Logging

PROGRESS.jsonl event schema, grep patterns, and how to inspect every prompt and tool call.

Explore
Hands-off Rules

Hands-off Rules

Per-project glob patterns the bot cannot touch. Violations trigger automatic rollback.

Explore
AI Safety Architecture

AI Safety Architecture

Hard rules, adversarial input model, and why structure beats better prompts for agent safety.

Explore
● Why PolyLever

Traditional AI Coding vs PolyLever

Autonomous agents fail predictably when structure is replaced by instructions. PolyLever encodes discipline as code — gates the model cannot bypass.

● Traditional AI Coding

Prompt-Based

  • Agent says the task is done
  • Tests may fail after completion
  • Empty diffs can still look successful
  • Protected files rely on instructions
  • Review happens after the damage
  • Logs are partial or hidden
Enforcement: trust the agent
● PolyLever System

Gate-Enforced

  • Task is not done until checks pass
  • Tests, diff, and scope are verified every cycle
  • Hands-off files are blocked by rule
  • Work runs in .bot-worktree on bot/work
  • Failed cycles roll back automatically
  • Prompts, responses, tool calls, and diffs land in PROGRESS.jsonl
Enforcement: Code-levelVerified Safe
● Tutorial & Demo

See the gate in action

Watch how PolyLever orchestrates agents, enforces verification, and maintains a complete audit trail — cinematic presentation of real workflow patterns.

Cycle Execution

Dispatcher orchestrates engineer → verification → reviewer with session budgets and structured SITREPs.

$ gs session --budget=90
→ picker: myproject
→ engineer: running in .bot-worktree
→ verification: 2,052 tests passing
→ reviewer: scope_match ✓
→ commit: bot/work @ a3f91c2

Orchestrate with absolute control

Start with gs welcome, register a project, and run your first verified cycle. Your codebase deserves gates, not just prompts.

Get StartedGitHub