Repository Docs & Knowledge Base

Consolidated Spensara documentation repository (722 Markdown & architecture documents in ../repository)

Built Word Documents (.docx): Spensara Overview (.docx) Capability Assessment (.docx) Brink POS Ingestion Analysis (.docx) The Borg Ingestion Architecture (.docx)

Branches (328)

Branch-specific documentation across extract-raw-xml, feature-fleet-import, kds_cdc_improvments, life-cycle, and tenat-admin.

branches/extract-raw-xml/etl/docs/features/ETL/index.md 3,445 bytes · Updated Oct 23, 2026 10:44 AM EDT

Raw File

ETL Feature Index

This directory is organized into two layers:

epics/ - problem-space backlog items that define the permanent ETL capability areas
slices/ - delivery slices that group implementation work across one or more epics
warehouse-data/ - reference documentation for curated warehouse tables and other ETL-owned data surfaces

Epics

epics/01-etl-platform-foundation/
epics/02-tenant-redshift-warehouse-template/
epics/03-s3-landing-replay-and-failure-storage/
epics/04-programmable-source-adapters/
epics/05-source-adapter-kitchen-go-kds/
epics/06-source-adapter-brink-pos-api/
epics/07-curated-data-modeling-serving-views/
epics/08-secrets-security-isolation-controls/
epics/09-tenant-access-control-store-group-management-rbac/
epics/10-source-onboarding-schema-governance/
epics/11-cross-tenant-analytics-query-path/
epics/12-etl-reliability-replay-backfill/
epics/13-etl-observability-cost-control/
epics/14-evaluation-framework-for-testing-monitors/

Slices

slices/01-redshift-foundation/ - first cross-epic delivery slice proving Redshift on current functionality without full ETL scope
slices/02-redshift-synthetic-data-feed/ - historical bridge of simulator-generated KDS data into the earlier Redshift source-mirror curated contracts
slices/03-single-store-redshift-runtime-read-path/ - historical switch of single-store backend reads and AI data access to tenant-resolved approved Redshift objects
slices/04-kds-monitor-serving-contract-migration/ - historical migration of KDS monitor prompts from kdsdev.* to the earlier approved Redshift contracts
slices/05-unified-curated-foundation-and-bootstrap/ - reset the warehouse contract so staging stays source-shaped and curated becomes the stable business-named tenant read model
slices/06-kds-staging-to-unified-curated-adapter/ - implement the first staging -> curated adapter using synthetic KDS data and business-named KDS tables
slices/07-kds-monitor-unified-curated-migration/ - plan the monitor-spec migration from historical KDS table names to the current business-named curated KDS contract

Direction Note

Slices 01 through 04 document the earlier source-mirror curated.<system>_<table> direction that was used to bootstrap Redshift work in this branch.

The current target direction for ETL foundations is defined by:

slices/05-unified-curated-foundation-and-bootstrap/
slices/06-kds-staging-to-unified-curated-adapter/

In the new direction:

staging remains source-shaped raw data
curated is the stable business-named operational read schema for every integrated system
prompts, endpoint contracts, and monitor-agent consumer migration stay in separate follow-up work
slices/07-kds-monitor-unified-curated-migration/ plans the first monitor-spec migration onto the new KDS curated.kitchen_* surface

../../flows/etl-ingestion.md - end-to-end ETL ingestion, warehouse load, and curated publication flow
redshift-serverless-dev-setup.md - step-by-step AWS Redshift Serverless dev setup and current app connection flow

Usage Rule

Add new long-lived ETL capability definitions under epics/.

Add new implementation stages that span multiple epics under slices/.

Each slice should have its own index.md that defines scope, linked epics, key documents, and explicitly excluded work.