Owner Commissioning
Production Readiness
Fail-closed commissioning view for environment, secrets, infrastructure, rollback, disaster recovery and external authorities.
Commissioning decision
Readiness score
11%
Blocking conditions
12
Release version
v43-production-release-evidence-gate
Owner action register
| Domain | Check | Severity | Owner | Status | Required action |
|---|---|---|---|---|---|
| ENVIRONMENT | Production mode | CRITICAL | Platform Engineering | READY | |
| ENVIRONMENT | HTTPS public URL | HIGH | Platform Engineering | BLOCKED | |
| SECRETS | Managed PostgreSQL secret | CRITICAL | Database Owner | BLOCKED | |
| SECRETS | OIDC authority | CRITICAL | Identity Owner | BLOCKED | |
| SECRETS | Immutable evidence storage | HIGH | Evidence Owner | BLOCKED | |
| INFRASTRUCTURE | Immutable OCI image | CRITICAL | Release Engineering | BLOCKED | |
| INFRASTRUCTURE | Container registry | HIGH | Release Engineering | BLOCKED | |
| INFRASTRUCTURE | Production cluster | CRITICAL | Infrastructure Owner | BLOCKED | |
| INFRASTRUCTURE | TLS certificate | CRITICAL | Security Owner | BLOCKED | |
| INFRASTRUCTURE | Observability endpoint | HIGH | SRE Owner | BLOCKED | |
| ROLLBACK | Rollback evidence | CRITICAL | Release Engineering | BLOCKED | |
| DISASTER_RECOVERY | Restore evidence | CRITICAL | Business Continuity Owner | BLOCKED | |
| EXTERNAL_AUTHORITY | External approval provider | HIGH | Governance Owner | BLOCKED | |
| EXTERNAL_AUTHORITY | Independent assessor | MEDIUM | Board Assurance Owner | WARNING |
Production acceptance gates
| Gate | Owner | Evidence | Production meaning | Status |
|---|---|---|---|---|
| Repository integrity | Engineering | Package contains GTOS App Router, API routes, governance docs, audit scripts and Design System gates. | The release candidate is a structured application repository, not a collection of static mockups. | |
| Build and dependency verification | Engineering | npm ci, TypeScript, ESLint, audit suite, production build and npm audit are mandatory before release acceptance. | The release must remain reproducible and free of moderate-or-higher dependency vulnerabilities. | |
| Docker image verification | External Runner | Dockerfile and docker-verification workflow are prepared; real docker build requires Docker-enabled runner. | Container acceptance is not claimed until a Docker daemon or CI runner creates and smoke-tests the image. | |
| CI/CD evidence | External Runner | GitHub/GitLab pipeline must run npm ci, lint, typecheck, audits, build and Docker verification. | Production Ready requires a reproducible external CI result, not only local sandbox execution. | |
| Live deployment acceptance | Operations | Production URL must pass /api/health, /api/readiness, SEO, legal, security header and RFQ smoke checks. | A deployment is accepted only after the live host proves runtime health and route availability. | |
| Playwright browser E2E | External Runner | Browser tests must execute on an unrestricted runner because sandbox Chromium policies can block localhost. | User journeys are accepted only after real browser execution against preview or production deployment. | |
| Legal and compliance boundary | Compliance | Legal Center, Export Control Notice, no-public-offer disclosures, Trust/Vault/RFQ gates are present. | GTOS remains a controlled B2B operating system, not an uncontrolled public offer or retail storefront. | |
| Security acceptance boundary | Security | Security headers, RBAC/ABAC matrix, audit evidence hashing and API permission gates are enforced in code. | Application-side security controls are ready for external penetration/security validation. |
External verification checklist
- 01Run npm ci on the release candidate archive or clean repository checkout.
- 02Run npm run typecheck and npm run lint.
- 03Run npm run audit:all and npm run audit:production-release-evidence.
- 04Run npm run build and archive build logs.
- 05Run npm audit --audit-level=moderate and archive the zero-vulnerability result.
- 06Run docker build on a Docker-enabled runner and record image digest.
- 07Run container smoke test against /api/health and /api/readiness.
- 08Run Playwright E2E on unrestricted CI/browser runner.
- 09Deploy to preview/production URL and run live acceptance smoke checks.
- 10Attach CI logs, deployment URL, Docker image digest and E2E report to release evidence.
Release claim policy
Forbidden claim: Do not claim live production readiness from local code checks alone.
Approved claim: Release candidate handoff ready for external production verification.