# Workstreams and Ownership Plan

## 1. Workstream Summary

1. Product and Governance
2. Persistence and Data Model
3. Proposal Lifecycle Service
4. API and Security
5. Normalizer and Validator
6. Flow Builder Integration
7. Observability and Operations
8. QA and Release Management

## 2. Responsibility Matrix

## 2.1 Product and Governance

Scope:
1. Status model approval
2. Approval policy and RBAC model
3. Tenant policy decision model

Responsible:
- Product Owner
- Architecture Lead

Accountable:
- Platform Owner

Consulted:
- Security Lead
- Compliance Lead

Informed:
- Delivery Team

## 2.2 Persistence and Data Model

Scope:
1. Proposal table and events table
2. Schema constraints and indexes
3. Migration and rollback safety

Responsible:
- Backend Engineer A

Accountable:
- Backend Lead

Consulted:
- DBA

Informed:
- QA Lead

## 2.3 Proposal Lifecycle Service

Scope:
1. State transitions
2. Transition guards
3. Event append on transitions

Responsible:
- Backend Engineer B

Accountable:
- Backend Lead

Consulted:
- Product Owner

Informed:
- QA Lead

## 2.4 API and Security

Scope:
1. Generate/get/approve/reject/open endpoints
2. Feature flags
3. RBAC and authz checks

Responsible:
- Backend Engineer C

Accountable:
- Backend Lead

Consulted:
- Security Lead

Informed:
- Product Owner

## 2.5 Normalizer and Validator

Scope:
1. Canonical mapping
2. Structural graph checks
3. Tenant policy checks

Responsible:
- Backend Engineer D

Accountable:
- Architecture Lead

Consulted:
- Flow Builder SME

Informed:
- QA Lead

## 2.6 Flow Builder Integration

Scope:
1. Generate with AI entry
2. Proposal review and warnings display
3. Open proposal into existing draft flow

Responsible:
- Frontend Engineer A

Accountable:
- Frontend Lead

Consulted:
- Backend Lead

Informed:
- Product Owner

## 2.7 Observability and Operations

Scope:
1. Proposal telemetry events
2. Dashboards and alerting
3. Runbook and rollback updates

Responsible:
- Platform Engineer

Accountable:
- SRE Lead

Consulted:
- Backend Lead

Informed:
- Product Owner

## 2.8 QA and Release Management

Scope:
1. API integration test suite
2. Regression testing for existing flow builder path
3. Release readiness checklist

Responsible:
- QA Lead

Accountable:
- Engineering Manager

Consulted:
- Product Owner

Informed:
- All Teams

## 3. Critical Hand-offs

1. Persistence complete -> Lifecycle service starts
2. Lifecycle service complete -> API implementation starts
3. Normalizer stable -> UI proposal review starts
4. API plus UI stable -> full QA cycle starts
5. QA sign-off -> controlled rollout starts

## 4. Governance Cadence

1. Daily delivery sync (15 min)
2. Mid-week architecture checkpoint
3. End-week release readiness review
4. Weekly production rollout review during expansion