Skip to main content

Built

Core. Manifests, write-ahead ledger, dependency-aware rollback with retries, verification read-backs and reconciliation, scopes, observe and advise modes, risk scoring, policy as code with tests and versions, content checks, kill switches (global and scoped), secret redaction, signed evidence, reports (HTML, PDF, period reports) and files / SQLite / PostgreSQL stores. Approvals. Queued, argument-bound, single use, expiring, persisted; quorum and group routing, escalation on timeout, delegation, break-glass with a recorded reason and evidence reference (approvals). Manifests and policy as files. Versioned, signable manifest registry with drafts, approval (four-eyes), deprecation and rollback; policy versions; reversi lint, reversi test, manifest suggestion from MCP tools, schema-drift detection; reversi apply for GitOps; hot reload (GitOps). Gateway. Observe-first start with no manifests, classification banner, enforce / advise / observe, input and output schema validation, per-manifest timeout and retry, verification through the upstream, several upstreams, allow/deny, approvals, operator endpoint with rollback tools, Streamable HTTP with auth, egress check of upstream URLs, the console on its own port (gateway). What-if. Capture of redacted calls, policy simulation, replay with changes, speculative comparison of plans, impact preview (simulation). Operations. HTTP API with roles, key rotation and OIDC; the operator console with three modes, manifest and policy editors, rollback execution, alerts, keys, holds and retention; Prometheus metrics, OpenTelemetry traces, structured logs and alerts; notification channels (Slack, Teams, email, PagerDuty, Opsgenie, signed webhook) with routing (notifications); retention, legal holds and ledger anchoring (retention); egress allowlist and data-residency labels. Ecosystem. The CLI (cli), TypeScript and Python SDKs, Pydantic bindings, framework adapters (LangGraph, CrewAI, OpenAI Agents SDK, FastMCP, Claude Code hook), fourteen connectors with a certification suite, the trace viewer, a Dockerfile, a Compose stack, a Helm chart (with an optional writable registry volume) and CI definitions.

Built, not yet verified against real systems

Tested with fakes or local stand-ins only. See limits for the detail.
  • The fourteen connectors against live services (the filesystem connector is local and real).
  • Notification channels and OpenTelemetry export against the real products.
  • The Python framework adapters against installed LangGraph, CrewAI, OpenAI Agents and FastMCP.
  • The Dockerfile, Compose stack and Helm chart (never built or installed; helm lint was not run).
  • The GitHub workflows, and the CI example in GitOps.

Not built

  • A Terraform provider and a Kubernetes operator. reversi apply and the Helm chart are the alternative.
  • OIDC browser redirect login for the console (login mode takes a pasted API key or OIDC access token).
  • A hosted control plane.
  • Go and Java SDKs.
  • Clustering with run hand-off between gateway or server processes.
  • Gateway passthrough of MCP resources, prompts and sampling.
  • An independent external security review of the code.