# Sprint Plan_ Founder CRM and Platform Planning

**Date:** 2026-04-18  
**Sprint Window:** 2026-04-18 to 2026-04-20  
**Status:** In Progress  
**Owner:** Sagnik  
**Reviewers:** Sayan, Sourik  
**Scope:** Founder-owned planning sprint for CRM, canonical domains, import layer, infra truth, and monolithic documentation  
**Purpose:** Define the sequencing and completion gates for the founder planning sprint.  
**Decision Boundary:** This sprint covers planning deliverables only. Code implementation is deferred.

## 1. Purpose

This sprint exists to make Project Velocity architecturally legible on the founder side before more implementation continues in parallel.

## 2. Sprint Goal

By the end of this sprint, Project Velocity should have one coherent founder-owned planning pack that defines the CRM core, canonical database domains, infrastructure truth, and monolithic documentation path.

## 3. Scope

- clone and adapt the template pack
- produce reconciliation and infra truth docs
- define CRM as a top-level module
- define canonical DB domains and route families
- define CSV-first import architecture
- define synthetic client graph brief
- create monolithic truth artifact starter

## 4. Non-Scope

- actual route implementation
- actual schema migration
- UI coding for CRM pages
- live connector implementation

## 5. Deliverables

- founder pack guide
- first-principles document
- PRD
- SRS
- sprint plan
- implementation blueprint
- execution backlog
- contracts/schema blueprint
- adapter spec
- DB/root API spec
- TypeScript module spec
- role spec
- deployment/ops/readiness spec
- dependency matrix
- reconciliation matrix
- infra/operator truth doc
- synthetic client graph swarm brief
- `Project Velocity Monolithic Truth.md`

## 6. Milestones

1. founder pack seeded and renamed
2. reconciliation and infra truth completed
3. CRM + DB architecture completed
4. execution and synthetic-data docs completed
5. monolithic truth artifact initiated

## 7. Integration Points

- `backend/main.py`
- `backend/api/routes_crm.py`
- `backend/api/routes_oracle.py`
- `backend/db/schema.sql`
- `backend/db/schema_addendum.sql`
- `app/src/App.tsx`
- `app/src/app/oracle/page.tsx`
- existing Sprint 1 handoff docs

## 8. Risks and Dependencies

- risk: stale Sprint 1 assumptions contaminating current planning
- risk: CRM and Oracle boundaries becoming muddled
- risk: overdesigning implementation details before approval
- dependency: current infra docs must remain accurate
- dependency: founder pack must not conflict with Sayan and Sourik packs

## 9. Acceptance Gates

- reconciliation matrix completed
- infra/operator truth completed
- CRM top-level module design completed
- canonical domain model completed
- synthetic data brief completed
- monolithic truth artifact started

## 10. Ownership

- Founder: CRM, import, client graph, monolithic truth
- Sayan: Oracle templates, inventory, admin/control surfaces
- Sourik: runtime, colony, orchestration, route-family implications

## 11. Timeline

Expected order:

1. reconciliation and infra
2. CRM and DB architecture
3. contracts, adapter, and frontend module planning
4. backlog and ticket slicing
5. synthetic-data brief
6. monolithic consolidation

## 12. Bottom Line

This sprint is successful if the next implementation pass no longer needs to invent the founder-side architecture while building it.