The Autonomous Stack
Release Gate Agent icon

Release Gate Agent · Dev · v1

GO/NO-GO release decisions from test evidence

Turn local release evidence into a clear, replayable GO, NO-GO, or GO-with-waivers decision. It is for release managers and service owners who need named accountability before a production change.

$3.00one-timePay with crypto

Buy on Gumroad → https://6355137346884.gumroad.com/l/tas-agent-release-gate-v1

release-management change-control risk

agent ⟶ theautonomousstack.xyz

01GET /api/v1/pack/agent-release-gate-v1

402 Payment RequiredPAYMENT-REQUIRED

02sign TransferWithAuthorization3.00 USDC · Base (eip155:8453)

03GET + PAYMENT-SIGNATURE

200 OKapplication/zip · 22 files

pay per pack over x402no account

What's inside

  • README.md
  • SOUL.md
  • PROMPTS.md
  • CHECKLIST.md
  • SPEC.md
  • CUSTOMIZE.md
  • OPERATING_COST_ESTIMATE.md
  • agent.py
  • llm_adapter.py
  • pack_memory.py
  • test_agent.py
  • smoke_test.sh
  • requirements.txt
  • deploy.sh
  • install.sh
  • agent-release-gate-v1.service
  • agent-release-gate-v1.json
  • fixtures/changes.json
  • fixtures/tests.json
  • fixtures/risks.json
  • fixtures/slo.json
  • fixtures/owners.json

The decision engine is fully offline and deterministic. An optional local LLM CLI can draft an explanation from the finished decision record; it cannot alter the verdict.

Quick start

python3 agent.py evaluate --input fixtures
python3 agent.py evaluate --input my-release-evidence --output decision.json
python3 agent.py verify --input my-release-evidence --record decision.json
bash smoke_test.sh

Provide changes.json, tests.json, risks.json, slo.json, and owners.json. See CUSTOMIZE.md for their schemas and integration points.

Decision flow

local evidence --> deterministic checks --> blockers / accepted risks --> signed record
                         |                         |                     |
                    tests, owners, SLO       named, dated waiver       replay later
Component Role Can change verdict?
Deterministic core Validates tests, ownership, risk acceptance, SLO and rollback plan Yes
Optional LLM CLI Writes reader-friendly decision prose No

This pack reads files only. It performs no network access, deployment, payment, or approval action. verify recalculates the complete record and rejects any changed, removed, or added output field.

Use a local model (Ollama)

The optional LLM step can also run on your own machine through Ollama, so no text leaves your server. No account and no API key.

ollama pull <model>               # any chat model you like
export PACK_LLM=ollama            # prefer Ollama even if a coding-agent CLI is installed
export PACK_OLLAMA_MODEL=<model>  # optional: default is the first chat model the server lists
python3 -c "import llm_adapter; print(llm_adapter.detect())"   # prints: ollama
  • PACK_OLLAMA_HOST points to another server (default http://127.0.0.1:11434); OLLAMA_HOST is also read when PACK_LLM=ollama.
  • PACK_OLLAMA_NUM_CTX sets the context size if your reports or prompts are long.
  • Without PACK_LLM, a local Ollama server is used only when no Claude Code, Kimi Code or Codex CLI is found.
  • If the server is down or the model is missing, the pack keeps working in its deterministic mode.

Learning memory (local and private)

Every LLM call this pack makes is journaled in ./.pack_memory/ next to the code, so the pack can improve for you. Nothing is ever sent anywhere.

  • What is kept: the task name, the masked input, the masked answer, status and latency. Keys, tokens, e-mails, phone numbers, IP addresses, card and IBAN numbers and personal paths are masked before writing; the system prompt is never stored.
  • Teach it: python3 pack_memory.py feedback last ok confirms a result, python3 pack_memory.py feedback last bad --fix "the right answer" corrects it. Confirmed and corrected runs are reused as validated examples when a similar input comes in. Unrated runs are never injected into a prompt.
  • Find similar cases: python3 pack_memory.py similar "some text" and python3 pack_memory.py clusters (groups of near-identical failures) work in plain Python, no model needed. Optional meaning-based matching uses an embedding model you already run locally: python3 pack_memory.py enable-semantic (Ollama on this machine only).
  • Share, only if you want: python3 pack_memory.py export writes an anonymised summary (counts, statuses, size buckets, no text) for you to review.
  • Control: PACK_MEMORY=0 turns it off, PACK_MEMORY_STORE_TEXT=0 keeps fingerprints only, python3 pack_memory.py purge --yes wipes it.