# Product Requirements Document (PRD)_ Multi-Surface Platform and Oracle Expansion

**Date:** 2026-04-16  
**Status:** Active planning artifact  
**Owner:** Sayan  
**Reviewers:** Sagnik, product and integration reviewers  
**Scope:** User-facing and operator-facing outcomes for tablets, phone edge apps, Oracle template system, inventory loading, and admin control plane  
**Purpose:** Define what product value this work must deliver.

## 1. Product Goal

Expand Project Velocity from a partially asymmetric surface set into a coherent suite where:

- tablets can run real field workflows
- phones can monitor and control the edge of the system
- Oracle can serve structured templates across all surfaces
- inventory can be loaded and maintained systematically
- admins can operate the whole suite safely

## 2. Target Users

- realtor and brand representatives
- internal operator teams
- property sales directors
- platform admins
- content and data operators

## 3. Core Product Outcomes

### 3.1 iPad App

- finish the residual pages
- update components to match current product direction

### 3.2 iPhone Edge App

- narrow mobile control surface
- lead and communication awareness
- alerts, status, notes, and fast actions
- communication-memory reminders and follow-up surfaces
- dedicated business communications surface for WhatsApp messaging and calling where supported
- cellular-call context and recording-import flow
- consent-based recording import and transcription workflows where supported
- provider-routed business communication ingestion where direct device capture is unavailable
- personal calendar surface for the assigned user

### 3.3 Android Tablet App

- same structural product as iPad
- Android-native presentation and layout discipline

### 3.4 Android Phone Edge App

- Android counterpart of iPhone edge app
- same product scope, platform-specific implementation
- optional deeper capture hooks only where default-handler, enterprise, or approved provider conditions make them defensible

### 3.5 Oracle Template Product

- chaptered template book
- subchapter categorization
- seed JSON template database
- later synthetic expansion through Kimi

### 3.6 Inventory Pipeline

- operator-friendly add/edit flow
- backend ingestion path
- future client self-service readiness

### 3.7 Admin Control Plane

- login
- status visibility
- installation and debugging surface
- system operation tooling

### 3.8 Calendar and Insight Loop

- exclusive user calendar
- reminders derived from conversations
- transcript insight extraction
- CRM and QD-score update recommendations

## 4. Product Boundaries

In scope:

- native and near-native product surfaces
- backend-facing contracts
- schema and template expansion
- admin operations surface
- communication memory built from supported capture, supported provider APIs, and operator-assisted imports
- user calendar derived from communication outcomes
- transcript and speaker-segregation pipeline

Out of scope for this run:

- unsupported device-level interception features
- uncontrolled consumer messaging hacks
- replacing the current backend architecture

## 5. Success Criteria

- iPad residual work is clearly closed or ticketed with acceptance
- Android tablet plan maps directly to iPad structure
- phone edge apps have bounded, platform-realistic MVP scope
- communication-memory strategy is explicit per channel, not hand-waved
- user calendar and insight loop are explicitly modeled
- Oracle template book and DB model are explicit
- inventory ingestion path is defined and buildable
- admin control plane scope is concrete

## 6. Bottom Line

The value of this work is not more screens. The value is a coherent, device-aware, Oracle-backed operating suite that can be extended without multiplying technical debt.