# Sprint Plan_ Multi-Surface Platform and Oracle Expansion

**Date:** 2026-04-16  
**Status:** Sprint definition  
**Owner:** Sayan  
**Reviewers:** Sagnik and integration reviewers  
**Scope:** Sequence the implementation so contracts and backend truths land before broad UI divergence.

## 1. Sprint Goal

Create a safe execution path for the multi-surface expansion by landing shared contracts, schema direction, and ownership boundaries before device-specific implementation fragments.

## 2. Sprint Milestones

### Milestone 1: Orientation and inventory of current truth

- audit current iPad app
- audit WebOS modules
- audit Oracle routes and schema
- audit inventory corpus and current backend shapes

### Milestone 2: Shared contract and schema baseline

- define shared entities
- define Oracle template chapter model
- define inventory ingest contracts
- define admin auth and role boundaries

### Milestone 3: Tablet and phone architecture split

- finalize iPad residual list
- define Android tablet parity map
- define phone edge MVP scope

### Milestone 4: Backend route and data readiness

- extend current backend routes and schema
- avoid parallel service drift

### Milestone 5: Surface implementation starts

- iPad residual completion
- Android tablet scaffold
- phone edge MVP scaffold
- admin control plane scaffold

## 3. Mandatory Order

The team should not start with broad mobile UI polish.

Correct order:

1. contracts
2. schema
3. backend routes
4. tablet parity map
5. phone edge MVP map
6. UI implementation

## 4. Deliverables This Sprint Must Produce

- filled architectural packet
- real file ownership map
- Oracle schema extension plan
- template book outline
- inventory ingest plan
- admin surface plan

## 5. Known Dependencies

- inventory source files from Sagnik are still pending
- communications ingestion provider choices may still need final confirmation
- Android implementation should not start deep UI work before iPad parity mapping is complete