first commit

staging/README.md

@@ -0,0 +1,24 @@
+# Staging readiness gate
+
+This directory does not contain a staging deployment and does not authorize any
+real integration. It provides a separate, network-disabled validation root for
+the non-secret decisions in `PRODUCTION_INPUTS.md`.
+
+1. Complete the business and technical decisions in `PRODUCTION_INPUTS.md`.
+2. Copy `staging.env.example` to `staging.env` and replace the `TBD` values with
+   non-secret metadata only. `staging.env` is ignored by Git and Docker builds.
+3. Run:
+
+   ```bash
+   docker compose -f compose.staging.yaml run --rm readiness
+   ```
+
+The gate rejects incomplete values, local endpoints, fake provider selections,
+embedded secret-like settings, and unsafe secret-source choices. The readiness
+container has no network. A pass means only that the required non-secret inputs
+are structurally complete; it does not prove provider access, security, business
+approval, compatibility, or production readiness.
+
+The actual staging application composition must be created only after these
+inputs and provider contracts are approved. Secrets must be injected from the
+approved external mechanism and must never be copied into this repository.

staging/staging.env.example

@@ -0,0 +1,17 @@
+# NON-SECRET METADATA ONLY. Copy to staging/staging.env after decisions are made.
+# The copied file is ignored. Never put tokens, passwords, access keys, webhook
+# secrets, private keys, credentials, or customer information in either file.
+APP_ENV=staging
+STAGING_APPROVED_BY=TBD
+STAGING_PUBLIC_ORIGIN=TBD
+STAGING_S3_ENDPOINT=TBD
+STAGING_S3_BUCKET=TBD
+STAGING_DATABASE_MODE=TBD
+STAGING_SECRET_SOURCE=TBD
+STAGING_BACKUP_DESTINATION=TBD
+STAGING_FREIGHT_PROVIDER=TBD
+STAGING_PAYMENT_PROVIDER=TBD
+STAGING_ERP_PROVIDER=TBD
+STAGING_WHATSAPP_PROVIDER=TBD
+STAGING_ALERT_OWNER=TBD
+STAGING_ROLLBACK_OWNER=TBD