forked from sagnik/Project_Velocity
sayan
eeb684b46c
#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
171 lines
4.5 KiB
Markdown
171 lines
4.5 KiB
Markdown
# Sayan Work Assignment_ Sprint 1 Execution Slice
|
|
|
|
**Date:** 2026-04-17
|
|
**Status:** Active execution slice
|
|
**Assignee:** Sayan
|
|
**Purpose:** Reduce a broad multi-surface assignment into the Sprint 1 slice that must be completed before broader implementation fans out.
|
|
|
|
## 1. Why This Slice Exists
|
|
|
|
Your broader assignment is intentionally large. Sprint 1 should not try to fully build every tablet, every phone surface, the entire Oracle template library, the complete inventory pipeline, and the full admin system simultaneously.
|
|
|
|
Sprint 1 must establish the execution truth that later implementation will build on.
|
|
|
|
The active communications priority for this slice is:
|
|
|
|
- cellular calls
|
|
- WhatsApp messages
|
|
- WhatsApp voice calls
|
|
- user calendar integration
|
|
- transcript and insight pipeline
|
|
|
|
SMS is deferred.
|
|
|
|
## 2. Sprint 1 Deliverables
|
|
|
|
### 2.1 iPad Residual Audit
|
|
|
|
Produce:
|
|
|
|
- page-by-page residual inventory
|
|
- component gap list
|
|
- acceptance criteria for each unfinished area
|
|
- safe implementation order
|
|
|
|
### 2.2 Android Tablet Parity Map
|
|
|
|
Produce:
|
|
|
|
- information-architecture parity against iPad
|
|
- screen map
|
|
- shared modules versus Android-specific modules
|
|
- implementation scaffold recommendation
|
|
|
|
### 2.3 Phone Edge MVP Definition
|
|
|
|
Produce:
|
|
|
|
- shared iPhone and Android phone edge MVP
|
|
- channel-by-channel communication capture matrix for cellular calls and WhatsApp
|
|
- control-surface scope
|
|
- reminder and follow-up scope
|
|
- note and import flows
|
|
- business WhatsApp inbox and calling surface scope
|
|
|
|
This is a product-definition and contract-definition step first, not a blind UI sprint.
|
|
|
|
### 2.4 Oracle Template Taxonomy
|
|
|
|
Produce:
|
|
|
|
- chapter tree
|
|
- subchapter tree
|
|
- component families
|
|
- two to three seed JSON examples per representative class
|
|
|
|
### 2.5 Inventory Ingest Contract Draft
|
|
|
|
Produce:
|
|
|
|
- property ingest entity model
|
|
- media ingest model
|
|
- operator edit model
|
|
- batch import lifecycle
|
|
- validation and error surfaces
|
|
|
|
### 2.6 Admin Bounded Action List
|
|
|
|
Produce:
|
|
|
|
- admin roles
|
|
- supported actions
|
|
- unsafe actions explicitly excluded
|
|
- required audit trail events
|
|
|
|
### 2.7 Backend Schema Extension Draft
|
|
|
|
Produce:
|
|
|
|
- Oracle schema additions
|
|
- mobile-edge route additions
|
|
- template DB route additions
|
|
- communication-memory entities
|
|
- calendar entities and action contracts
|
|
- transcript and diarization entities
|
|
|
|
### 2.8 Calendar and Agent Action Slice
|
|
|
|
Produce:
|
|
|
|
- user-exclusive calendar model
|
|
- NemoClaw write permissions and confirmation rules
|
|
- event creation, edit, and reminder contract
|
|
- relationship between communications, reminders, and calendar entries
|
|
|
|
## 3. Communication Capture Matrix You Must Deliver
|
|
|
|
For each of these channels, classify:
|
|
|
|
- supported direct ingestion
|
|
- provider-routed ingestion
|
|
- operator-assisted import only
|
|
- blocked or deferred
|
|
|
|
Channels:
|
|
|
|
- PSTN or business telephony calls
|
|
- WhatsApp business messages
|
|
- WhatsApp voice calls
|
|
- optional email follow-on note
|
|
- calendar writeback trigger path
|
|
- CRM or QD-score side effect path
|
|
- WhatsApp business messages
|
|
- WhatsApp voice calls
|
|
|
|
For each channel, also define:
|
|
|
|
- consent model
|
|
- transcription path
|
|
- speaker segregation path
|
|
- reminder extraction path
|
|
- backend provenance field requirements
|
|
|
|
## 4. Mandatory Sprint 1 Output Shape
|
|
|
|
By the end of Sprint 1, Sayan should have produced:
|
|
|
|
- a concrete parity matrix for iPad and Android tablet
|
|
- a bounded edge-app MVP with channel reality accounted for
|
|
- schema and contract extensions for communication memory
|
|
- schema and contract extensions for calendar and transcript intelligence
|
|
- Oracle template taxonomy and seed examples
|
|
- inventory ingest contract shape
|
|
- admin action boundary list
|
|
|
|
## 5. What Sprint 1 Must Not Attempt
|
|
|
|
- full cross-platform implementation all at once
|
|
- unsupported mobile interception experiments
|
|
- broad backend rewrites
|
|
- speculative schema expansion without route and contract alignment
|
|
|
|
## 6. Sequence
|
|
|
|
1. Audit current iPad and WebOS truth.
|
|
2. Produce Android tablet parity map.
|
|
3. Produce communication capture matrix for cellular and WhatsApp.
|
|
4. Produce communication-memory contract additions.
|
|
5. Produce calendar model and NemoClaw action rules.
|
|
6. Produce Oracle template taxonomy and seed JSON structure.
|
|
7. Produce inventory ingest contract draft.
|
|
8. Produce admin action boundary list.
|
|
9. Only then begin bounded implementation slices.
|
|
|
|
## 7. Bottom Line
|
|
|
|
Sprint 1 is the execution-shaping sprint.
|
|
|
|
If this slice is done correctly, later implementation will be parallelizable and reviewable.
|
|
|
|
If this slice is skipped, the broader assignment will fragment into conflicting mobile assumptions, weak schemas, and hard-to-merge surface work.
|