Ramp Production Readiness Gate

Overview

Convert launch assumptions into evidenced gates. Review the exact artifact, environment, OAuth authority, data handling, endpoint contracts, reconciliation, incident controls, and rollback before any production write.

Prerequisites

• Identify the Ramp application, environment, business entities, affected data and workflows, accountable owner, and rollback boundary.
• Read references/official-docs.md and re-check endpoint schemas, scopes, limits, and support status before a live operation.
• Use synthetic fixtures or Ramp sandbox until production access and business effects are explicitly approved.
• Prepare approved secret storage and a sanitized evidence location.

Current Contract

• Production is isolated from sandbox and requires its own Ramp application, credentials, scopes, redirects, subscriptions, and approved business access.
• Third-party integrations use Authorization Code; internal server integrations may use Client Credentials.
• Card, accounting, bill, reimbursement, and other writes create business effects that need endpoint-specific idempotency and reconciliation.
• Current OpenAPI and guide exports may supersede copied examples or generated client assumptions.