VRP Working List

Active Work In Front Of The AI Team

Quiet top layer. Drill into WO records and evidence only when needed.
Status: Not every workstream was shown in the first VRP brief. This page is the active working list inside VRP.

0. TOP PRIORITY - VRP Path To Revenue

Important Q: Does this move us closer to a qualified lead, signed customer/investor, paid certification, or repeatable sales process?

1. VRP AI Command Center

Build an Enforcer-led assistant surface inside VRP for sales help, lead follow-up, task assignment, AI delegation, and approval gates.

2. WhatsApp In VRP

Use the Frappe WhatsApp add-on path and wrap it with VRP consent, evidence, lead/deal linkage, tasks, and approval controls.

  • Open Project PROJ-0012
  • Status: AI install/security/architecture/UI reviews complete
  • Next: BB/base VRP sandbox proof before production
  • Gate: no customer send without approval

3. BB Base VRP

Build a base VRP system on the BB server only after inventory and drift checks are accepted.

  • Open Project PROJ-0013
  • Status: plan produced by SG
  • Inventory/drift reports produced by SC and SGPT
  • Gate: no build until approval

4. Source Of Origin Fields

Added VRP fields for source tracking across leads, investors, partners, and evidence-linked records.

  • Open Project PROJ-0014
  • Status: applied on MIUSA and Verity
  • Includes CRM Lead, CRM Deal, CRM Organization, Contact, Supplier, VRP Investor Campaign, VRP Investor Onboarding, VRP AGE, VRP WO. Legacy ERPNext Lead, Opportunity, and Customer remain preserved as background records, not the primary CRM menu.
  • Verity investor onboarding state-field drift fixed

5. TCI Wiki History

Canonical uploaded history HTML was verified, edited to make FFA onboarding proposed, and kept as source material.

  • Open Project PROJ-0015
  • Status: uploaded and hash verified
  • FFA date language changed to proposed
  • HTML source-of-origin section removed after field clarification

6. CRM Package SSOT

CRM package is live in VRP/ERPNext as the SSOT for CRM Organization, CRM Lead, CRM Deal, notes, tasks, calls, and notifications.

  • Open Project PROJ-0016
  • Status: sidecar flow proved
  • Use as reference, not direct production install
  • Gate: integrate only through BB/base VRP or approved VRP path

7. VGATE Dual-Site Sync Rule

Standing rule for Adam-facing work: follow VGATE, attach work to an exposed WO, show it in the WO/Projects area, and sync both VRPs unless Adam explicitly scopes a one-site exception.

8. Interactive WO Action Buttons

Make VRP portal buttons action-oriented instead of static: Investigate, Clarify, Deploy Gate, Enforcer Validate, and Comments.

9. BOD / User / Sales Contact Update

Updated users, contacts, and confirmed governance profiles. Corrected classification: not all listed people are BOD; John Polyak is CFO; Aaron Reiser is Sales.

  • Open Project PROJ-0020
  • Open WO-2026-00006
  • Confirmed BOD roles: Luci Sheehan, Larry Light, Pete Thomas Petropoulos, Marty William Martin
  • Management/CFO: John Polyak
  • Sales: Aaron Reiser
  • Contacts/users only pending role confirmation: Timothy Wesselman

10. User Type And Role Authority

Admin-facing guide defining Administrator, System Manager, System User, Website User, BOD, Management, Sales, Finance, Project, Website, Customer, and Supplier roles.

11. Sales Agency / AFF Onboarding

Build the sales group and agency lane for companies sending leads, sales opportunities, websites, and influencer/social activity into VRP with AFF enrollment and portal ACL.

12. S00562 AI Discovery Starter - Austin / Zenyte Gate

Revenue-critical onboarding lane for the paid AI Discovery Starter order. Build the repeatable portal flow before any more customer contact.

Operating Rules

  • Briefs go in VRP first.
  • Keep top layer quiet; use deep links for evidence.
  • Segment work by topic to prevent contamination and drift.
  • No build execution without WO approval.
  • Sync both VRPs for WO/project-visible work unless Adam explicitly approves a one-site exception.