Reverse ETL — subservice (Data)
Service line: Data
Subservice (display): Reverse ETL
Folder slug: reverse-etl
Linear subservice label: reverse-etl (create in workspace if missing; see linear-cleanup-taxonomy.md §4)
Status: Taxonomy entry is a proposal pending Head of Delivery confirmation — see Decision 6 in the service definition README.
Scope
Warehouse outbound syncs to operational and marketing systems: reverse ETL tools, native connectors, model/table exposure, scheduling, monitoring, and break-fix. Most client-facing packaging today is ongoing retainer / maintenance rather than a fixed-scope project name.
Not in scope for “this subservice” by label alone: Ingestion-only work (Data Platform), semantic/mart design without outbound sync (Data Modeling)—though tickets may carry multiple labels when work spans buckets.
Offerings
| Folder | Status |
|---|---|
| (none yet) | Add {offering-slug}/ with offer.md, sop.md, implementation-plan.md, linear-template.md when the first packaged offer is defined. |
Related elsewhere: Reverse ETL appears inside activation-style engagements (e.g. Edge-to-Activation); use label reverse-etl on retainer and sustaining reverse ETL tasks so views and capacity line up with this subservice.