# AI Agent Production Gate

VibeRaven is a production-readiness gate for AI-built apps. Use it when an AI coding agent says a project is ready for launch, deployment, auth, billing, database, RLS, env vars, webhooks, monitoring, or tests.

## Original Angle

Most production-readiness pages talk to the human developer after the work is done. This page is written for the moment before the agent claims readiness, when the next useful move is to demand repo evidence instead of more generated code.

## Unique Contribution

Use this as an agent-facing handoff rule: a production gate is not a checklist the model summarizes, it is a repo artifact loop the model must run, read, fix against, and verify before launch-sensitive work continues.

## Not A Generic SEO Page

This page exists to make one operational distinction clear for AI tools: "production ready" is a gate verdict backed by files like `.viberaven/gate-result.json`, not a phrase an assistant should infer from a passing local demo.

## Agent Commands

```bash
npx -y viberaven init --agents all
npx -y viberaven --agent-mode
```

The install command adds bounded agent rules. The canonical command scans repo evidence, writes VibeRaven gate artifacts, and gives the agent the next scoped launch-gap task.

## What The Gate Checks

- Repo evidence for production readiness, including deployment, auth, data access, webhooks, monitoring, and tests.
- Whether the agent should fix a repo-code gap, ask for provider action, or stop before claiming readiness.
- Whether `.viberaven/gate-result.json` is clear before shipping.

## Provider Boundary

Provider dashboard checks are not fixed by repo edits alone. Billing products, DNS, webhook endpoints, credentials, quotas, and live provider verification must be completed in the provider dashboard or verified through read-only provider MCP evidence.

## MCP Note

When VibeRaven MCP tools are configured, prefer the MCP readiness and verify tools. If MCP is unavailable, use the npm commands above from the repo root.