warehouse-lake-architect

What problem does it solve?

This Skill designs the analytical destination for a multi-tenant SaaS so reporting and analytics do not devolve into swamp-like lakes or undocumented view sprawl. It helps you choose the right estate class, define governed zones, and keep tenant isolation and PII rules intact as data moves into analytics.

Core Features & Use Cases

• Estate Class Selection: Chooses warehouse, lake, or lakehouse based on workload shape, governance needs, and team maturity.
• Zone and Mart Design: Defines raw, conformed, and curated zones with ownership, contracts, retention, and access rules.
• Tenant-Safe Analytics: Preserves tenant keys through every zone and designs per-tenant access paths for customer-facing analytics.
• Modeling and Layout Guidance: Recommends dimensional or wide modeling per mart, SCD policy, partitioning, formats, and compaction strategy.
• Governed Adoption Path: Adds catalog registration, ingestion handoff boundaries, PII handling, and incremental migration from existing analytics sprawl.

Quick Start

Ask the Skill to design our analytical estate for a small SQL-heavy team, including zones, marts, tenant isolation, and the adoption path from our current analytics setup.