sayan/Project_Velocity
1
1
Fork 0
forked from sagnik/Project_Velocity
Code Issues Pull Requests Activity
Files
13f0cf8abe5be38bebef8428b8fcca047f31c30c
Project_Velocity/.Agent Context/Sayan's Docs/Sayan Multi-Surface and Oracle Delivery Pack/Sayan Work Assignment_ Multi-Surface Platform and Oracle Expansion.md
sayan eeb684b46c feat: Ipad app production readiness, Colony orchestration, Social posting (#44) 
#38 Ipad app production readiness, Colony orchestration, Social posting

Co-authored-by: Sayan Datta <sayan@Sayans-MacBook-Air.local>
Reviewed-on: sagnik/Project_Velocity#44
2026-05-03 18:30:38 +05:30

5.7 KiB
Raw Blame History

Sayan Work Assignment_ Multi-Surface Platform and Oracle Expansion

Date: 2026-04-16
Status: Active assignment handoff
Assignee: Sayan
Purpose: Define the exact work Sayan owns in this run, including current repository truths, scope boundaries, sequence, and merge discipline.

1. Assignment Summary

You are being assigned the multi-surface product expansion lane for Project Velocity.

This includes:

  1. iPad app residual pages and component updates
  2. iPhone edge app
  3. Android tablet parity app
  4. Android phone edge app
  5. Oracle schema coverage for these component classes
  6. Oracle template book and seed JSON template DB
  7. Kimi Synthetic Data downstream plan
  8. inventory loading and edit pipeline
  9. admin control panel surface
  10. communication-memory strategy across supported business channels
  11. user calendar and transcript-intelligence path for NemoClaw-assisted follow-up

This is a broad assignment, but it is not a freeform rewrite.

2. Current Repo Truth You Must Respect

WebOS

  • Project_Velocity/app/

Relevant current files:

  • Project_Velocity/app/src/App.tsx
  • Project_Velocity/app/src/app/oracle/page.tsx
  • Project_Velocity/app/src/hooks/useCrmBootstrap.ts
  • Project_Velocity/app/src/components/modules/

iPad app

  • Project_Velocity/iOS/velocity/velocity/

Relevant current feature folders:

  • Features/Dashboard
  • Features/Inventory
  • Features/Oracle
  • Features/Sentinel
  • Features/Settings

Backend and Oracle

  • Project_Velocity/backend/

Relevant files:

  • Project_Velocity/backend/main.py
  • Project_Velocity/backend/api/routes_oracle.py
  • Project_Velocity/backend/api/routes_crm.py
  • Project_Velocity/backend/oracle/router_v1.py
  • Project_Velocity/backend/oracle/schema_oracle.sql

Inventory source corpus

  • Project_Velocity/db assets/Inventory/

3. Your Concrete Scope

3.1 iPad App

You own:

  • residual page audit
  • component gap audit
  • completion plan
  • implementation of the open gaps you can safely land

3.2 Android Tablet App

You own:

  • parity map against current iPad information architecture
  • recommended project structure
  • initial implementation scaffold

3.3 Phone Edge Apps

You own:

  • iPhone edge app definition
  • Android phone edge app definition
  • shared edge MVP scope
  • explicit platform-safe feature boundaries

These phone apps are not full WebOS copies. They are compact operator surfaces for:

  • quick lead and communication awareness
  • alerts
  • note capture
  • transcription visibility
  • communication-memory reminders
  • calendar follow-up actions
  • approved communication control hooks

3.4 Oracle Template System

You own:

  • template chapter taxonomy
  • subchapter taxonomy
  • seed JSON examples
  • DB model proposal for storing them

3.5 Kimi Synthetic Data

You own the downstream plan. The expected output is a separate Kimi Synthetic Data workstream definition that consumes the template seed DB.

3.6 Inventory Loading Pipeline

You own:

  • schema and contract planning
  • operator-friendly add/edit flow planning
  • ingest pipeline planning

Sagnik still needs to provide additional property source files. Build the pipeline shape now, not fake completeness.

3.7 Admin Control Panel

You own:

  • admin surface scope
  • route and action plan
  • implementation blueprint

4. What You Must Read First

  1. Introduction for Sayan.md
  2. Sayan Work Assignment_ Sprint 1 Execution Slice.md
  3. 14 - Platform Reality and Communications Capture Strategy.md
  4. 01 - First Principles_ Multi-Surface Platform and Oracle Expansion.md
  5. 05 - Implementation Blueprint_ Multi-Surface Apps WebOS Edge and Oracle Delivery.md
  6. 07 - Contracts and JSON Schemas_ Templates Inventory Edge Capture.md
  7. 09 - Oracle Schema and Root API Spec_ Multi-Surface Platform.md
  8. 13 - Implementation Ticket Breakdown and Dependency Matrix_ Multi-Surface Platform.md

5. What You Must Not Do

  • do not create a second backend center
  • do not create a second Oracle schema truth
  • do not build phone capture around unsupported or hidden OS behavior
  • do not assume a managed work phone automatically grants system-level message or call access
  • do not casually rewrite active WebOS modules owned by others
  • do not block other branches by broad refactors

6. Collaboration and Merge Discipline

Respect each other's code.

  • narrow PRs by workstream
  • do not reformat unrelated files
  • do not rename broad folders casually
  • isolate backend route additions by route family
  • isolate schema changes and get review before stacking UI on top

7. Recommended Execution Order

  1. audit current truth
  2. define shared contracts
  3. define schema additions
  4. define iPad residual list
  5. define Android tablet parity map
  6. define phone edge MVPs with platform-safe constraints
  7. define template book and DB seed plan
  8. define inventory ingest path
  9. define admin control plane
  10. implement in bounded slices

8. Bottom Line

Your job is to turn the current Velocity codebase into a more complete multi-surface product without breaking the existing center of gravity. Start from contracts and schema. Then build the surfaces.

Reference in New Issue View Git Blame Copy Permalink