# Flow Connector Live Proof

Decision: ready for first authorized tenant; final connector green requires credential, sync, replay and SLA sign-off.

## Proof phases

### 1. Credential intake
- Owner: Integrations
- Proof: Tenant-approved credential or sandbox credential, provider, scope, expiry and owner are registered.
- Pass: Credential can be tested without exposing raw secret values in UI or artifacts.

### 2. Provider health check
- Owner: Provider Ops
- Proof: Setup endpoint, auth check, provider latency, throttling state and failure reason are archived.
- Pass: Provider status is customer-safe and operator-actionable.

### 3. Happy-path sync
- Owner: Domain owner
- Proof: Create/update event reaches provider and provider ID is stored on Flow object.
- Pass: Flow can reconcile internal ID to external ID without manual lookup.

### 4. Replay and recovery
- Owner: Reliability
- Proof: Webhook replay or retry path is executed for one known event and one failed/recovered event.
- Pass: Retry outcome, attempt count, final status and customer-safe explanation are visible.

### 5. SLA sign-off
- Owner: Ops lead
- Proof: Delivery certainty, queue backlog, replay success and known limitations are signed off.
- Pass: Connector can be sold as live-supported for the selected provider and tenant.

## Provider order
- [ ] CRM: HubSpot · lead/contact create, update replay, dedupe
- [ ] Helpdesk: Zendesk or Freshdesk · ticket create, comment sync, status update, webhook replay
- [ ] PMS: Mews or Apaleo · block create, update, release/rollback, provider block ID
- [ ] Calendar: Google Calendar or Outlook · conflict check, create, reschedule, cancel
- [ ] Messaging: Twilio · dispatch, delivery receipt, failed reason, fallback retry

## Guardrails
- [ ] Do not paste provider secrets into screenshots, tickets or exported proof packs.
- [ ] Every live-proof run must include tenant id, provider id, owner, timestamp and environment.
- [ ] A provider can be marked live-supported only for the exact event types that passed.
- [ ] Failed replay is acceptable only when the recovery reason, owner and retest state are archived.
- [ ] Customer-facing connector status must explain degradation without exposing raw logs.