Implementation Blueprint_ Multi-Surface Apps WebOS Edge and Oracle Delivery

Date: 2026-04-16
Status: Implementation map
Owner: Sayan
Reviewers: Sagnik, frontend/backend integration reviewers
Scope: Repository mapping and execution boundaries for the multi-surface workstream.

1. Repository Centers To Respect

WebOS: Project_Velocity/app/
backend: Project_Velocity/backend/
iPad native: Project_Velocity/iOS/velocity/velocity/
inventory assets: Project_Velocity/db assets/Inventory/

2. Recommended Workstream Ownership

WebOS and shared web contracts

Project_Velocity/app/src/
focus:
- shared UI semantics
- Oracle and inventory contracts
- admin control plane surface

iPad residual completion

Project_Velocity/iOS/velocity/velocity/Features/
focus:
- Dashboard
- Inventory
- Oracle
- Sentinel
- Settings

Android tablet

iPhone edge

Android phone edge

backend extension

Project_Velocity/backend/api/
Project_Velocity/backend/oracle/
Project_Velocity/backend/services/

3. Backend Extension Areas

Recommended route families:

routes_mobile_edge.py
routes_inventory.py
existing Oracle route extension instead of Oracle route replacement
routes_admin_surface.py

4. Schema Extension Areas

Existing Oracle schema reference:

Project_Velocity/backend/oracle/schema_oracle.sql

Recommended additions:

template chapter tables
template example tables
inventory property and ingestion tables
transcription job and communication event tables where approved
admin action audit tables

5. Merge Safety Rule

Keep ownership disjoint:

tablet native work isolated by platform directory
backend route additions isolated by route family
schema changes staged and reviewed centrally
WebOS changes limited to the specific modules under Sayan scope

2.1 KiB Raw Blame History