# Platform Integrations Roadmap

Status: Draft
Parent: `docs/ROADMAP.md`

# Phase P0 — Core Wiring

- [x] Auth integration
- [ ] Feature flags integration
- [ ] Telemetry integration
- [ ] Diagnostics integration
- [ ] Blob integration

# Phase P1 — Extraction

- [ ] Summarization integration
- [ ] Metadata enrichment integration
- [ ] Task extraction integration
- [ ] Fallback behavior for extraction failures

# Phase P2 — Orchestration

- [ ] MCP integration rules
- [ ] Optional jobs/webhooks integration
- [ ] A2A handoff patterns
- [ ] Correlation/request ID propagation review

# Phase P3 — Readiness

- [ ] Verify `platform-service` dependencies
- [ ] Verify `extraction-service` fallback behavior
- [ ] Verify telemetry ingestion
- [ ] Verify diagnostics ingestion
- [ ] Verify blob flows
- [ ] Verify production-safe defaults

# Integration Decisions To Lock

- [x] Which `platform-service` modules are required in v1
- [x] Which extraction tasks are in v1
- [x] Which integrations are optional/deferred
- [ ] Which flows require feature flags from day one

# Progress Notes

- 2026-03-10 — Backend scaffold now includes explicit placeholders for platform integration:
  - JWT verification aligned with `bytelyst-platform` issuer
  - `PLATFORM_SERVICE_URL`, `EXTRACTION_SERVICE_URL`, and `MCP_SERVER_URL` added to backend env bootstrap
  - product-specific APIs remain in `learning_ai_notes/backend/` rather than common platform
- Current v1 required shared dependencies:
  - `platform-service` for auth and later flags/telemetry/diagnostics/blob
  - `extraction-service` for summarization, metadata enrichment, and task extraction
  - `mcp-server` for scoped tool exposure and orchestration

# Open Questions

- Which feature-flag-controlled flows need to exist before first integrated release?
- Should blob upload authorization be mediated solely by platform-service SAS flows for v1?
- Should extraction calls start synchronously in product-backend routes or via async jobs first?

# Blockers

- No platform integration smoke checks have been executed yet because dependencies are not installed and no local env is configured.

# Deferred

- Telemetry and diagnostics client wiring
- Blob metadata + upload/download flow wiring
- Optional jobs/webhooks integration
- A2A handoff implementation

# Done When

- [ ] Shared platform dependencies are explicit and stable
- [ ] Failure modes are documented
- [ ] Product can rely on platform services without hidden assumptions
