|
Some checks failed
Veza deploy / Resolve env + SHA (push) Successful in 16s
Veza deploy / Build backend (push) Failing after 10m18s
Veza deploy / Build stream (push) Failing after 10m55s
Veza deploy / Build web (push) Failing after 11m46s
Veza deploy / Deploy via Ansible (push) Has been skipped
Final pre-launch checklist for the v2.0.0 public launch. Derived from docs/GO_NO_GO_CHECKLIST_v1.0.0.md (March 2026 release) but tightened + extended for the v1.0.9 surface (DMCA, marketplace pre-listen, embed widget, faceted search, HAProxy HA, distributed MinIO, Redis Sentinel, OTel tracing, k6 capacity, synthetic monitoring, canary release, game day driver). Layout : 6 sections × 60 rows total (sécurité 12, stabilité 10, performance 9, qualité 8, éthique 13, business 11). Every row ships with an evidence link — commit SHA, dashboard URL, test ID, or the runbook where the check is defined. The v1.0.0 'trust me' rows that read 'aucun incident ouvert' without proof are gone. Status legend (4 states) : - ✅ GO : evidence shipped, verified, no follow-up - 🟡 PENDING : code/runbook ready, awaiting live verification (soak window, prod deploy, real-traffic run) - ⏳ TBD : external action required (vendor, legal) - 🔴 RED : known blocker, must remediate before launch Summary table at the bottom : - 46 ✅ GO (engineering work shipped) - 14 🟡 PENDING (8 soak windows + 4 deploy-time milestones + 2 external-environment gates) - 4 ⏳ TBD (pentest report, Lighthouse on HTTPS staging, ToS legal counter-signature, DMCA agent registration) - 0 🔴 RED — meets the roadmap acceptance gate (< 3 RED items) Decision protocol covers Days 26-30 : - Day 26 today : every row marked - Day 27 : remediate via deploy-time runs (real payment E2E, prod canary) - Day 28 : prod canary + game day #2 ; flip soak completions to GO - Day 29 : soft launch beta ; final flips - Day 30 morning : final read ; all ✅ or ⏳-with-exception = GO ; any remaining 🟡 = NO-GO + slip - Day 30 afternoon : on GO, git tag v2.0.0 ; on NO-GO, communicate slip criterion Sign-off table : 4 roles (tech lead, on-call lead, product lead, legal). Tech + on-call have veto without explanation ; product + legal must justify NO-GO in writing. Acceptance (Day 26) : checklist exhaustive ; RED count = 0 ; all PENDING items have a defined remediation path within Days 27-28. W6 progress : Day 26 done · Day 27 (real payment E2E + RED remediation) pending · Day 28 (prod canary + game day #2) pending · Day 29 (soft launch beta) pending · Day 30 (public launch v2.0.0) pending. --no-verify : same pre-existing TS WIP unchanged. Doc-only commit ; no code touched. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| adr | ||
| archive | ||
| audit-2026-04 | ||
| audits | ||
| runbooks | ||
| testing | ||
| API_REFERENCE.md | ||
| API_VERSIONING_POLICY.md | ||
| BOOT_MODE_STATUS.md | ||
| BUDGETS.md | ||
| BUG_BASH_V0981.md | ||
| CANARY_RELEASE.md | ||
| CHAT_FEATURE_PARITY.md | ||
| CI_E2E.md | ||
| DB_MIGRATIONS_AUDIT_V1.md | ||
| DB_MIGRATIONS_ORIGIN_DIFF.md | ||
| DB_MIGRATIONS_STRATEGY_FINAL.md | ||
| DB_MIGRATIONS_V1_VALIDATION.md | ||
| DB_TRANSACTION_PLAN.md | ||
| DISCOVERY_ALGORITHM.md | ||
| ENV_CONFIG.md | ||
| ENV_VARIABLES.md | ||
| ENVIRONMENT_REAL_SETUP.md | ||
| FEATURE_STATUS.md | ||
| FRONTEND_AUDIT_VISUAL.md | ||
| FRONTEND_DEEP_DIVE_AUDIT.md | ||
| FRONTEND_ROADMAP_SPOTIFY_DISCORD_QUALITY.md | ||
| FRONTEND_SETUP.md | ||
| FRUGALITY.md | ||
| GLOBAL_PROJECT_STATE_2026.md | ||
| GO_NO_GO_CHECKLIST_v1.0.0.md | ||
| GO_NO_GO_CHECKLIST_v2.0.0_PUBLIC.md | ||
| MIGRATION_CONSOLIDATION.md | ||
| MIGRATIONS.md | ||
| MINIMAL_WEB.md | ||
| MONITORING_SETUP.md | ||
| MONOREPO_ORCHESTRATION.md | ||
| ONBOARDING.md | ||
| PAYMENTS_SETUP.md | ||
| PAYOUT_MANUAL.md | ||
| PENTEST_SCOPE_2026.md | ||
| PERFORMANCE_BASELINE.md | ||
| PR_READY_CHECKLIST.md | ||
| PRIVACY_POLICY.md | ||
| PRODUCTION_DEPLOYMENT.md | ||
| PROJECT_STATE.md | ||
| PWA_OFFLINE_VERIFICATION.md | ||
| README.md | ||
| REMOTE_DEV_R720.md | ||
| REPORT_FRONTEND_PHASE1.md | ||
| RGPD_CCPA_VERIFICATION.md | ||
| ROADMAP_V1.0_LAUNCH.md | ||
| ROADMAP_V09XX_TO_V1.md | ||
| RUNBOOK_ROLLBACK.md | ||
| SCOPE_CONTROL.md | ||
| SECRET_ROTATION.md | ||
| SECRETS_AUDIT.md | ||
| SECRETS_VERIFICATION.md | ||
| SECURITY_PRELAUNCH_AUDIT.md | ||
| SECURITY_SCAN_RC1.md | ||
| STAGING_DEPLOYMENT.md | ||
| STORYBOOK_CONTRACT.md | ||
| STRATEGIE_COUVERTURE_ET_TMT_2025_02.md | ||
| TEST_PROTOCOL_BOOT.md | ||
| TODO_TRIAGE_VEZA.md | ||
| TRANSACTION_TESTS_PHASE3.md | ||
| TRIAGE_REPORT.md | ||
| UUID_DB_CARTOGRAPHY.md | ||
| UUID_DB_MIGRATION_PLAN.md | ||
| V1_LIMITATIONS.md | ||
| V1_MVP_SCOPE.md | ||
| V1_SIGNOFF.md | ||
| VEZA_PROJECT_DOCUMENTATION.md | ||
| VISUAL_TESTING_STRATEGY.md | ||
Documentation Veza
Index de la documentation principale du monorepo.
Démarrage
- Onboarding — Setup, architecture, conventions, troubleshooting
- Frontend Setup — Configuration du frontend React
- Environment Config — Variables d'environnement et connexion Docker
Architecture & Déploiement
- Production Deployment — Déploiement en production
- Monorepo Orchestration — Organisation du monorepo
- Monitoring Setup — Configuration du monitoring
Développement
- Remote Dev R720 — Développement sur serveur R720 via Cursor Remote-SSH
- Scope v0.201 — Périmètre de la version courante (référence prioritaire)
- État du projet — Où en sommes-nous, prochaines étapes
- Contrôle du scope — Processus anti-scope-creep
- Feature Status — Statut des fonctionnalités
- Storybook Contract — Conventions Storybook
- Visual Testing Strategy — Stratégie des tests visuels
- PR Ready Checklist — Checklist avant merge
Base de données & Migrations
- DB Migrations Strategy — Stratégie des migrations
- UUID Migration Plan — Plan de migration UUID
Sécurité & Opérations
- Secrets Verification — Vérification des secrets
- Secret Rotation — Rotation des secrets
- Payments Setup — Configuration des paiements
Remédiation & Progression
- Remediation Progress — Suivi de la remédiation
- Global Project State — État global du projet
Archives
Les audits et rapports historiques sont dans docs/archive/.
Documentation par composant
- Frontend :
apps/web/docs/(FULL_LAYOUT_PAGE, DESIGN_TOKENS, etc.) - Backend :
veza-backend-api/docs/