# Sayan Multi-Surface and Oracle Delivery Pack Guide

**Date:** 2026-04-16  
**Status:** Active work packet  
**Owner:** Sagnik  
**Primary Assignee:** Sayan  
**Reviewers:** Sagnik, integration owners for WebOS, iOS, backend, and schema  
**Scope:** Multi-surface product expansion across iPad, iPhone Edge, Android Tab, Android Phone Edge, Oracle schema expansion, template database, inventory ingestion, and admin control plane  
**Purpose:** Provide a complete, implementation-grade handoff set for Sayan so he can execute a bounded but broad workstream without reconstructing architecture from scattered files.

## 1. Why This Pack Exists

Sayan is not being assigned a single screen or a single file. He is being assigned a coordinated expansion of Project Velocity across:

- existing iPad app completion
- new iPhone edge app
- new Android tablet app
- new Android phone edge app
- Oracle schema expansion
- Oracle template book and JSON template database
- Kimi Synthetic Data follow-on path
- inventory loading pipeline
- admin control plane

Without a disciplined packet, this will fragment into duplicated UI, duplicated schemas, unsupported mobile assumptions, and merge conflicts.

## 2. Current Repository Truth

Existing repository centers already matter:

- WebOS frontend: `Project_Velocity/app/`
- FastAPI backend: `Project_Velocity/backend/`
- native iPad foundation: `Project_Velocity/iOS/`
- Oracle schema and routes: `Project_Velocity/backend/oracle/`
- inventory asset corpus: `Project_Velocity/db assets/Inventory/`
- operational ingress and deployment truth: `Project_Velocity/infrastructure/`

This packet extends those surfaces. It does not replace them.

## 3. Reading Order

Read these in order:

1. [Introduction for Sayan.md](./Introduction%20for%20Sayan.md)
2. [Sayan Work Assignment_ Multi-Surface Platform and Oracle Expansion.md](./Sayan%20Work%20Assignment_%20Multi-Surface%20Platform%20and%20Oracle%20Expansion.md)
3. [Sayan Work Assignment_ Sprint 1 Execution Slice.md](./Sayan%20Work%20Assignment_%20Sprint%201%20Execution%20Slice.md)
4. [14 - Platform Reality and Communications Capture Strategy.md](./14%20-%20Platform%20Reality%20and%20Communications%20Capture%20Strategy.md)
5. [01 - First Principles_ Multi-Surface Platform and Oracle Expansion.md](./01%20-%20First%20Principles_%20Multi-Surface%20Platform%20and%20Oracle%20Expansion.md)
6. [02 - PRD_ Multi-Surface Platform and Oracle Expansion.md](./02%20-%20PRD_%20Multi-Surface%20Platform%20and%20Oracle%20Expansion.md)
7. [03 - SRS_ Multi-Surface Platform and Oracle Expansion.md](./03%20-%20SRS_%20Multi-Surface%20Platform%20and%20Oracle%20Expansion.md)
8. [04 - Sprint Plan_ Multi-Surface Platform and Oracle Expansion.md](./04%20-%20Sprint%20Plan_%20Multi-Surface%20Platform%20and%20Oracle%20Expansion.md)
9. [05 - Implementation Blueprint_ Multi-Surface Apps WebOS Edge and Oracle Delivery.md](./05%20-%20Implementation%20Blueprint_%20Multi-Surface%20Apps%20WebOS%20Edge%20and%20Oracle%20Delivery.md)
10. [06 - Execution Backlog_ Multi-Surface Apps Oracle Templates Inventory Admin.md](./06%20-%20Execution%20Backlog_%20Multi-Surface%20Apps%20Oracle%20Templates%20Inventory%20Admin.md)
11. [07 - Contracts and JSON Schemas_ Templates Inventory Edge Capture.md](./07%20-%20Contracts%20and%20JSON%20Schemas_%20Templates%20Inventory%20Edge%20Capture.md)
12. [08 - Adapter Detailed Implementation Spec_ Mobile Edge Inventory Admin.md](./08%20-%20Adapter%20Detailed%20Implementation%20Spec_%20Mobile%20Edge%20Inventory%20Admin.md)
13. [09 - Oracle Schema and Root API Spec_ Multi-Surface Platform.md](./09%20-%20Oracle%20Schema%20and%20Root%20API%20Spec_%20Multi-Surface%20Platform.md)
14. [10 - Shared Surface Module Spec_ WebOS iPad Android Edge.md](./10%20-%20Shared%20Surface%20Module%20Spec_%20WebOS%20iPad%20Android%20Edge.md)
15. [11 - Delivery Roles and Ownership Spec_ Mobile Oracle Admin.md](./11%20-%20Delivery%20Roles%20and%20Ownership%20Spec_%20Mobile%20Oracle%20Admin.md)
16. [12 - Deployment Operations and Release Readiness_ Multi-Surface Platform.md](./12%20-%20Deployment%20Operations%20and%20Release%20Readiness_%20Multi-Surface%20Platform.md)
17. [13 - Implementation Ticket Breakdown and Dependency Matrix_ Multi-Surface Platform.md](./13%20-%20Implementation%20Ticket%20Breakdown%20and%20Dependency%20Matrix_%20Multi-Surface%20Platform.md)

## 4. Main Design Rule

One workstream, one packet, one truth.

The packet assumes:

- WebOS remains the canonical broad operator surface
- the current iPad app remains the native pattern reference for tablet field work
- phone edge apps are narrow operator control and capture surfaces, not full WebOS clones
- Oracle remains the analytical composition center
- backend schema authority remains in the current FastAPI root

## 5. Hard Constraints

- do not create parallel backend authority
- do not fork schema truth outside the current backend
- do not assume unrestricted call recording or message interception on iPhone or Android
- do not assume WhatsApp API alone can solve every voice and video ingestion need
- do not downgrade the business requirement for communication memory just because some capture paths are blocked
- solve the requirement through supported telephony, supported business messaging APIs, explicit imports, and operator-assist flows
- do not break existing iPad or WebOS code while extending it
- do not build merge-hostile ownership overlaps

## 6. Bottom Line

This is not a brainstorming folder. It is the implementation and handoff packet for a major product expansion that must respect the current Velocity root while opening the next execution lane for Sayan.