# SGPT DONE — SALES OPS RISK R2

Dispatch ID: AGE-SGPT-2026-05-14-SALES-OPS-RISK-R2
Assigned Agent: SGPT
Micro-Step Assigned: Redo Sales Ops risk review using SC ERP probe evidence only.
Check-In Declaration: SGPT checked in against AGE-SGPT-2026-05-14-SALES-OPS-RISK-R2 after reading AG-001, HO.md, COMMAND_GO_v2, AI_TEAM_AGE_REFRESH_2026-05-14.md, SGPT_INBOX.md, the R2 dispatch, WO-2026-MIUSA-SALES-OPS-001, and the SC ERP probe report.
Action Taken: Re-reviewed Sales Ops risk from the installed-state evidence in `/opt/veritize-docker/ops/queue/approval/2026-05-14_SC_DONE_SALES-OPS-ERP-PROBE.md`; superseded the rejected R1 assumptions; identified module-install, sequencing, and review-limit risks.
Evidence Submitted: SC probe shows `wk_miusa` has only 14 installed modules: `api_doc`, `auth_passkey`, `auth_totp`, `base`, `base_import`, `base_import_module`, `base_setup`, `bus`, `html_editor`, `iap`, `rpc`, `web`, `web_tour`, `web_unsplash`; SC probe also shows `account`, `board`, `crm`, `hr`, `mail`, `mass_mailing`, `project`, `purchase`, `sale`, `sale_management`, `stock`, and `website` are `uninstalled`; `crm.%` models return 0 rows; `sale.%` models return 0 rows; CRM/sale/sale_management view XML IDs return 0 rows; `fetchmail_server` relation does not exist; `ir_mail_server` returns 0 rows; only `ir_mail_server` exists among `fetchmail_server`, `ir_mail_server`, `mail_template`, and `sale_order_template`.
Result / Finding: NO-GO for implementation readiness; GO-WITH-CORRECTION for a new SC module-install planning dispatch. The rejected R1 risk review is superseded because it relied on unproven tools/modules/paths and assumed installed Sales Ops objects that SC proved do not exist on `wk_miusa`.
Check-Out Certification: This is a risk review only. No production files, databases, modules, views, mail servers, templates, permissions, or queues were mutated beyond this authorized SGPT report.

## R1 Assumptions Revoked / Superseded

The R1 risk review rejected at `/opt/veritize-docker/ops/queue/approval/2026-05-13_REJECT_SALES_OPS_SGPT_RISK_R1.md` remains rejected and is superseded by this R2 review.

Revoked assumptions:

- `crm.lead`, `sale.order`, sales quote templates, CRM stages, Sales dashboards, and mail templates are not available for review on `wk_miusa` because SC proved CRM, Sales, Sale Management, Mail, Project, Mass Mailing, Website, and Account are uninstalled or absent.
- Any prior reference to `erp-access-tool`, `SalesOpsModule.*`, `PricingModule.*`, or `/config/pricing/monthly/constraints` remains inadmissible because the R2 dispatch prohibits those references and the SC probe does not prove them.
- SGrok XML ID assumptions are not implementation-ready because SC proved CRM/Sales view XML IDs return 0 rows.

## Risks Of Installing Required Odoo Community Modules On `wk_miusa`

| Risk | Finding | Required control |
|---|---|---|
| Dependency expansion | `wk_miusa` is barebones with only 14 base/web modules installed; installing CRM/Sales/Mail/Account/Project/Website will materially change the database schema and menus. | SC must produce a module dependency plan before installation and perform BU-FIRST. |
| Schema creation | `crm.%` and `sale.%` models return 0 rows, and `mail_template` / `sale_order_template` tables do not exist. | Treat module install as first production mutation, not as configuration-only work. |
| Mail activation | `fetchmail_server` relation does not exist and `ir_mail_server` has 0 rows. | Install/configure Mail/fetchmail/SMTP in a separate micro-step after module plan and before CRM email automation. |
| Quote capability | `sale` and `sale_management` are uninstalled and quote template tables are absent. | Quote workflow cannot be validated until Sales/Sale Management objects exist. |
| View/dashboard assumptions | CRM/Sales view XML IDs return 0 rows. | SGrok and SG reviews must be rerun against actual installed XML IDs after module installation. |
| Permissions | Current groups/views for CRM/Sales are not proven because modules are absent. | Access groups must be listed from live ERP after install before Adamjr/affiliate permissions are granted. |
| Data migration | Existing partner/contact/product readiness is UNKNOWN from the SC probe. | SC must run a separate read-only data inventory before importing leads, products, CRM stages, or quote templates. |

## Sequencing Risks

1. Module install must be its own PTF micro-step with BU-FIRST, rollback plan, and exact module list.
2. Data migration must wait until SC proves installed models and table names for CRM, Sales, Mail, and Project.
3. Mail config must wait until Mail/fetchmail tables exist and must use vault-only credentials.
4. CRM stages cannot be safely created until `crm` is installed and SC proves stage model names and XML IDs.
5. Quote templates cannot be safely created until `sale_management` is installed and SC proves `sale_order_template` availability or the actual Odoo version equivalent.
6. Permissions cannot be assigned until the relevant CRM/Sales/Mail/Project groups exist and are listed.
7. VIRA must verify module state, model existence, view XML IDs, mail server config, quote rendering, and permissions before any DONE/COMPLETE claim.

## Cannot Be Reviewed Until Modules Are Installed

- CRM pipeline behavior, because no `crm.%` models exist.
- Sales order / quote behavior, because no `sale.%` models exist.
- Sales quote templates, because `sale_order_template` table does not exist.
- Mail template behavior, because `mail_template` table does not exist.
- Incoming mail routing, because `fetchmail_server` relation does not exist.
- Outgoing email behavior, because `ir_mail_server` has 0 rows.
- CRM/Sales dashboard XML IDs, because the SC view XML ID query returned 0 rows.
- Adamjr and affiliate permissions, because CRM/Sales/Project group records are not proven by the SC probe.

## File Location Table

| Artifact | Path |
|---|---|
| AGE refresh | `/opt/veritize-docker/ops/mcp/AI_TEAM_AGE_REFRESH_2026-05-14.md` |
| SGPT pointer | `/opt/veritize-docker/ops/mcp/SGPT_INBOX.md` |
| R2 dispatch | `/opt/veritize-docker/ops/queue/agents/sgpt/inbox/2026-05-14_DISPATCH_SALES-OPS-RISK-R2.md` |
| SC ERP probe evidence | `/opt/veritize-docker/ops/queue/approval/2026-05-14_SC_DONE_SALES-OPS-ERP-PROBE.md` |
| R1 rejection | `/opt/veritize-docker/ops/queue/approval/2026-05-13_REJECT_SALES_OPS_SGPT_RISK_R1.md` |
| Work order | `/opt/veritize-docker/ops/wo/open/WO-2026-MIUSA-SALES-OPS-001.md` |
| SGPT outbox report | `/opt/veritize-docker/ops/queue/agents/sgpt/outbox/2026-05-14_DONE_SGPT_SALES-OPS-RISK-R2.md` |
| SGPT approval report | `/opt/veritize-docker/ops/queue/approval/2026-05-14_SGPT_DONE_SALES-OPS-RISK-R2.md` |