# Integration and go-live checklist

Use this checklist as the launch gate for the VEGA77 CS Agent. Do not go live until every required item has an owner, status, and sign-off.

Status legend: `Todo`, `In progress`, `Blocked`, `Done`.

---

## 1. Scope and ownership

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 1.1 | Confirm production scope for first release: AI answers routine questions, escalates payment/tech/account issues, and sends Telegram alerts. | Zev / RR | Todo | Client agrees what is live on day one. |
| 1.2 | Confirm that CS remains the bridge to the customer. Payment and tech teams provide internal feedback; customer replies are handled by CS in LiveChat unless client changes SOP. | RR / Kate | Todo | Written SOP decision captured in handover docs. |
| 1.3 | Confirm who owns each queue: CS, payment, tech, admin/compliance, and who has authority to use kill switch. | RR / Ops lead | Todo | Role table approved. |
| 1.4 | Confirm support coverage hours and expected response SLA for escalations. | RR / Ops lead | Todo | SLA added to runbook. |
| 1.5 | Confirm go-live date, launch window, rollback owner, and emergency contact group. | RR / Zev | Todo | Launch window approved. |

## 2. Handover documentation

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 2.1 | Prepare and approve two handover documents. Doc A: specs, services, URLs, credentials, and environment values. Doc B: end-to-end user flow and integration flow. Overwrite existing docs if an older version exists. | Zev | Done | Latest docs are available before UAT sign-off. |
| 2.2 | Doc A location: `client_docs/09-Specs-Services-Links-Credentials.md`. Keep real secret values only in the secure local handoff source (`client_docs/CLIENT-TRY-GUIDE.txt`, `secrets/CREDENTIALS.txt`, or server `config/.env`). | Zev | Done | Public doc has service inventory; secure copy has actual credentials. |
| 2.3 | Doc B location: `client_docs/10-End-to-End-Flow-and-Integration.md`. | Zev | Done | Client can understand LiveChat, AI, Telegram, CS, payment, tech, and BO flow. |
| 2.4 | Update client docs index after the two docs are prepared. | Zev | Done | `client_docs/README.md` and `client_docs/index.html` link to the new docs. |

## 3. Product behavior and SOP alignment

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 3.1 | Update greeting behavior: greet once only at conversation start. Do not repeat greeting in follow-up replies. | Zev | Todo | UAT confirms no repeated greetings. |
| 3.2 | Keep customer replies short, direct, and professional. Avoid long explanations unless asked. | Zev | Todo | Kate/RR approve response tone. |
| 3.3 | Ask for missing player details one by one where practical, because players often answer only one question at a time. | Zev | Todo | Missing deposit, withdrawal, login tests pass. |
| 3.4 | Add/confirm scenario coverage for missing deposit, scam deposit, deposit to wrong bank, withdrawal pending, login/access issue, promo questions, account closure, and urgent complaint keywords. | Zev / Kate | Todo | Scenarios pass UAT. |
| 3.5 | Confirm escalation wording does not say payment/tech will reply directly if client SOP says CS replies to customer. | Zev | Todo | All handoff messages match CS bridge SOP. |

## 4. Knowledge base and RAG

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 4.1 | Confirm final promo source file. | Kate / Zev | Todo | Approved file in `knowledge/`. |
| 4.2 | Confirm final SOP source file. | Kate / Zev | Todo | Approved file in `knowledge/` or ingested uploads. |
| 4.3 | Remove outdated or duplicate knowledge files from active ingestion path. | Zev | Todo | No stale SOP/promo answers during UAT. |
| 4.4 | Rebuild or verify Chroma collections after knowledge changes. | Zev | Todo | `/stats` shows expected RAG counts. |
| 4.5 | Run promo and SOP spot checks against real client examples. | Kate / Zev | Todo | No hallucinated promo terms. |

## 5. LiveChat production integration

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 5.1 | Confirm production LiveChat path: website widget or direct LiveChat link. | RR / Kate | Todo | Final channel chosen. |
| 5.2 | Confirm LiveChat account ID and Personal Access Token are valid on production server. | Zev | Todo | Connector can poll and send messages. |
| 5.3 | Confirm LiveChat routing allows CS agents to see and take over escalated chats. | Kate / Ops | Todo | Human can reply in same customer thread. |
| 5.4 | Test normal AI reply through LiveChat. | Zev / Kate | Todo | Customer sees AI reply in LiveChat. |
| 5.5 | Test escalation through LiveChat. | Zev / Kate | Todo | Telegram alert fires and CS can continue in LiveChat. |

## 6. Telegram escalation operations

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 6.1 | Confirm payment, tech/CS, and admin Telegram groups. | RR / Kate | Todo | Correct groups exist. |
| 6.2 | Confirm bot is added to each group and can post alerts. | Zev / Ops | Todo | Test alert appears in each group. |
| 6.3 | Confirm group IDs are configured in `config/.env`: `TG_PAYMENT_GROUP_ID`, `TG_TECH_GROUP_ID`, `TG_ADMIN_GROUP_ID`. | Zev | Todo | Escalations route correctly. |
| 6.4 | Confirm normal Telegram discussion is internal only and customer-facing replies require `/reply <case_id> <message>`. | RR / Kate | Todo | SOP documented and trained. |
| 6.5 | Test `/reply` and `/resolve` with authorised operators only. | Zev / Ops lead | Todo | Approved Telegram reply reaches the same LiveChat customer thread. |
| 6.6 | Test `/status`, `/killswitch`, and `/resume` with authorised operators only. | Zev / Ops lead | Todo | Commands work and owner list is clear. |

## 7. BO / RPA go-live decision

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 7.1 | Decide whether BO/RPA live lookup is in day-one scope or post-go-live. | RR / Zev | Todo | Scope decision documented. |
| 7.2 | If day-one scope: verify BO credentials, login, IP/device restrictions, and lookup flows. | Zev / Ops | Todo | Live lookup works in controlled test. |
| 7.3 | If post-go-live: document that current release is RAG-first and BO lookup remains manual through staff. | Zev | Todo | Client runbook does not overpromise RPA. |

## 8. Infrastructure, DNS, and HTTPS

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 8.1 | Confirm VM public IP or reserve a static IP before final DNS. | Zev | Todo | IP will not change unexpectedly. |
| 8.2 | Confirm Namecheap A records for `@`, `agent`, and `docs` point to the production server if all hostnames are used. | RR / Zev | Todo | DNS resolves correctly. |
| 8.3 | Confirm Caddy hostnames match DNS. | Zev | Todo | HTTPS certs issue successfully. |
| 8.4 | Confirm cloud firewall allows TCP 80 and 443; restrict SSH and avoid exposing raw 8080 publicly. | Zev | Todo | HTTPS works; unnecessary ports are closed. |
| 8.5 | Confirm production stack starts with `deploy/docker-compose.production.yml`. | Zev | Todo | Containers restart cleanly. |
| 8.6 | Confirm `GET /health` returns `{"status":"ok"}` on production URL. | Zev | Todo | Health check passes. |
| 8.7 | Confirm `/stats` and dashboard require Basic Auth when public. | Zev | Todo | Unauthenticated `/stats` returns 401. |

## 9. Secrets and access control

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 9.1 | Confirm real secrets are only in secure stores or server `config/.env`, not public docs or git. | Zev | Todo | No secrets in tracked files or static docs. |
| 9.2 | Confirm required env values: Gemini key, LiveChat account/PAT, Telegram bot token/group IDs, BO credentials if used, dashboard username/password. | Zev | Todo | Production config complete. |
| 9.3 | Rotate any credentials that were shared in normal chat before production if risk is unacceptable. | RR / Zev | Todo | Client confirms rotation decision. |
| 9.4 | Confirm dashboard password is stored by client ops. | RR / Ops | Todo | Client can access without asking developer. |
| 9.5 | Confirm backup access for server, DNS, LiveChat, Telegram bot, and BO. | RR / Ops | Todo | No single-person access dependency. |

## 10. Testing and UAT

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 10.1 | Run automated tests. | Zev | Todo | Test suite passes. |
| 10.2 | Run production smoke test against HTTPS URL. | Zev | Todo | Health, dashboard auth, chat smoke pass. |
| 10.3 | Run UAT through web demo. | Kate / Zev | Todo | Core scenarios pass. |
| 10.4 | Run UAT through LiveChat. | Kate / Zev | Todo | Real customer path passes. |
| 10.5 | Validate payment escalation route. | Payment / Zev | Todo | Payment alert appears; CS reply process is clear. |
| 10.6 | Validate tech escalation route. | CS / Tech / Zev | Todo | Tech/CS alert appears after retries. |
| 10.7 | Validate admin/compliance escalation route. | Admin / Zev | Todo | Urgent/account closure route works. |
| 10.8 | Validate kill switch and resume. | Ops / Zev | Todo | AI can be paused and restored. |
| 10.9 | Validate no secrets appear in customer chat, Telegram alert, dashboard HTML, or `/stats`. | Zev | Todo | Security spot check passes. |

## 11. Launch day

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 11.1 | Freeze knowledge and code changes before launch window unless blocking issue. | Zev / RR | Todo | Stable release candidate. |
| 11.2 | Deploy production stack. | Zev | Todo | Services running on HTTPS. |
| 11.3 | Run final smoke tests. | Zev | Todo | Health, chat, LiveChat, Telegram pass. |
| 11.4 | Put CS team on monitoring standby. | RR / Kate | Todo | Humans ready to take over. |
| 11.5 | Enable widget/direct link for production users. | RR / Kate | Todo | Customer path is live. |
| 11.6 | Monitor first live conversations and escalations. | Zev / CS lead | Todo | No blocking issues in first launch window. |

## 12. Rollback and post-go-live

| # | Item | Owner | Status | Pass condition |
|---|------|-------|--------|----------------|
| 12.1 | Confirm rollback path: disable widget/AI, use kill switch, or revert production compose as needed. | Zev / Ops | Todo | Rollback instructions available. |
| 12.2 | Back up `data/` before major updates. | Zev | Todo | Restore point exists. |
| 12.3 | Track client feedback after launch and prioritise fixes. | Kate / Zev | Todo | Feedback list is maintained. |
| 12.4 | Schedule post-go-live review. | RR / Zev | Todo | First review booked. |

---

Related docs:

- [09-Specs-Services-Links-Credentials.md](09-Specs-Services-Links-Credentials.md)
- [10-End-to-End-Flow-and-Integration.md](10-End-to-End-Flow-and-Integration.md)
- [PRODUCTION-READINESS.md](PRODUCTION-READINESS.md)

Manual QA lists and developer test procedures are maintained in the source repository under **`docs/operations/`** (not published on `docs.ikon168.com`).