Greenlight

Greenlight

A reproducible deploy + verification harness for AI-built tools — every change ships through objective gates. Turn a domain plus API tokens into a live personal site and a self-verifying agentic deploy loop, with plug-and-play subdomain tools — web apps or MCP servers. Provider-agnostic and free-tier-first: the blog and each tool target Cloudflare Workers or Vercel, with OCI as the origin lane for stateful services.

You don't fork this repo — you install the CLI. greenlight init scaffolds a thin wrapper repo you own (your manifest + content) that depends on the published @rtrentjones/greenlight package and updates via pnpm update. The CLI edits declarative infra-as-code (Terraform you can read); your CI/CD applies it. Nothing is welded to one cloud, and there's no PaaS in the middle.

Quick start

npx -y @rtrentjones/greenlight init --domain you.dev   # scaffold the wrapper + gather base keys
pnpm greenlight add notes --lane mcp --target oci      # add a tool: emit infra + gather ITS keys
git push                                               # CI (infra.yml) runs `terraform apply`
pnpm greenlight verify notes --env prod                # the shared harness proves it

Full walkthrough: docs/getting-started.md.

Reviewer path (5 minutes)

1. Architecture in 3 min — docs/architecture.md (one spine, two planes).
2. See a real consumer — RTrentJones.dev (the thin wrapper) driving two live tools: BAMCP (mcp/oci, live — 401 = up + OAuth-gated) and HeistMind (next/vercel, live).
3. Run the gate — pnpm install && pnpm run check-all (typecheck + lint + tests + seam + boundaries).
4. Try it cold, no cloud creds — docs/demo.md (init --no-tokens → config → doctor → add … --no-tokens → preview).
5. Proof — npm · releases · security model.

Monorepo note: the repo root is private orchestration (name: greenlight, 0.0.0); the published package is cli/ → @rtrentjones/greenlight.

The loop

Every tool (and the blog) ships through the same gated loop — deploy → verify → promote. The verify gate is the same code CI and the agent run, so changes ship with objective confidence:

branch → change → preview → verify → develop/beta → verify → promote (gated develop→main) → prod → verify

See docs/architecture.md for how it all fits together and greenlight-v2.md for the spec.

Two planes over one spine

The manifest (greenlight.config.ts) + the CLI + the agent kit drive two related planes:

• Plane 1 — the infra editor. greenlight add/adopt: one manifest entry → emitted Terraform + gathered/verified tokens (secrets gather, straight to GitHub, never to disk/logs) + a wired agent kit. It edits IaC; CI/CD applies it.
• Plane 2 — the validation gate. One verify(baseUrl, spec) harness, six modes, combinable via an array — wired to promotion, not just test-writing.

How you consume it

This repo is the framework (one published npm package + git-tagged Terraform modules + a Claude Code plugin). Your site is a thin wrapper you own — created by greenlight init, depending on the package, owning only its manifest + content (the live example is RTrentJones.dev). You update the mechanics with pnpm update @rtrentjones/greenlight; you never merge framework code.

The deploy-verify-promote + per-provider skills ship as a Claude Code plugin (or greenlight agent sync):

/plugin marketplace add RTrentJones/greenlight
/plugin install greenlight@greenlight

Status

Framework built, published, and live — @rtrentjones/greenlight on npm (OIDC trusted publishing)

• Terraform modules tagged in lockstep. Both planes, the loop, lane templates, CI/CD, the provider-pack registry, the OCI free-tier path (network-as-IaC), and per-tool secret onboarding are in place; check-all green. Two real tools run on it end to end: BAMCP (mcp/oci, free A1 container instance) and HeistMind (next/vercel/supabase), each as a wrapper-centric subrepo with a green verify gate. MIT.