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:

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.

5.5 KiB Raw Blame History