Find My Data — actual-code architecture

This diagram reflects the code as built (not aspiration). One deployable server process hosts the API and an embedded durable worker; the worker can also run as a separate process against the same queue (bun run worker). All stores are SQLite tables behind role interfaces (ADR-0003); projections are rebuildable.

The staged pipeline (scan/pipeline.ts + intelligence/inference.ts)

Stage-cache keys encode the invalidation matrix: an eTag-only change (rename, permission, label) reuses content/features as cache hits with zero content fetches (tested); a cTag change re-fetches; an ensemble release re-scores from retained features with no connector dependency at all (tested).

What is real vs. gated here

Capability	State
Fixture connector, pipeline, ensemble, review, analyst, actions, audit	Implemented + tested (86 tests)
Azure OpenAI / Anthropic providers	Adapters implemented, config-gated, not exercised by tests
Microsoft Graph live connector (read)	Implemented + validated read-only against the live Contoso CDX tenant (ADR-0013). Mock stays the default/CI path.
Microsoft Graph live connector (write / label actions)	Not implemented — read-only app; write remains a separate protected path
Entra ID sign-in	Seam + production lockout; OIDC flow not active in this build
Purview label write (live)	Blocked on protected/metered API enablement
Teams / Exchange connectors	Not built — contracts and backlog only (see STATUS.md)

Data schema Capacity model

⌘I

​Find My Data — actual-code architecture

​The staged pipeline (scan/pipeline.ts + intelligence/inference.ts)

​What is real vs. gated here

Find My Data — actual-code architecture

The staged pipeline (scan/pipeline.ts + intelligence/inference.ts)

What is real vs. gated here