sync local
This commit is contained in:
29
README.md
29
README.md
@@ -196,29 +196,6 @@ Governance is not a checklist; it's embedded in the data layer.
|
||||
|
||||
---
|
||||
|
||||
## How to Use This Repo
|
||||
|
||||
### Deliverables
|
||||
- **`dbt/`**: Anonymized dbt models (staging, transforms, semantic views)
|
||||
- `models/staging/stg_*.sql` — Raw layer transformations
|
||||
- `models/transform/trf_*.sql` — Business logic
|
||||
- `models/distribute_ddl/sv_*.yml` — Semantic views with synonyms
|
||||
- **`cortex/`**: Governance config (information protection, access control, audit rules)
|
||||
- `cortex_governance_config.yaml` — Guardrails, freshness contracts, LLM policies
|
||||
- **`docs/`**: Architecture diagrams, decision logs
|
||||
- `architecture_dag.md` — Data flow Mermaid diagram
|
||||
- `decisions.md` — Architecture decision records (ADRs)
|
||||
- **`README.md`**: This file (the narrative for interviewers/stakeholders)
|
||||
|
||||
### How to Adapt This to Your Domain
|
||||
1. **Replace discount logic** with your domain (e.g., pricing tiers, contract terms, approval workflows)
|
||||
2. **Adjust freshness** (once-daily to hourly/real-time) based on your use case
|
||||
3. **Modify semantic dimensions** to match your business terminology
|
||||
4. **Update Cortex policies** for your personal-information and governance rules
|
||||
5. **Test with a small pilot** (5-10 users) before org-wide rollout
|
||||
|
||||
---
|
||||
|
||||
## Lessons Learned
|
||||
|
||||
### What Worked
|
||||
@@ -260,9 +237,13 @@ A: Yes. Adapt the dbt dialect (BigQuery: `jinja-sql`, Redshift: `redshift` profi
|
||||
A: For quote research, yes. If you need real-time pricing updates, escalate to hourly ELT. The architecture supports it; just change the schedule in your orchestrator.
|
||||
|
||||
**Q: What if I need to scale to 500+ users?**
|
||||
A: Semantic layer architecture scales horizontally. Snowflake handles concurrency. Monitor Cortex token usage and partition semantic views if queries slow down. dbt stays the same. The real issue comes when you need RLS requirements, this will enforce you to manager with additional tools or methods beyond Snowflake RBAC (Role Based Access Control).
|
||||
A: Semantic layer architecture scales horizontally. Snowflake handles concurrency. Monitor Cortex token usage and partition semantic views if queries slow down. dbt stays the same. The real issue comes when you need RLS requirements — this will require additional tools or methods beyond Snowflake RBAC.
|
||||
|
||||
**Q: Can I export this as a Snowflake Native App for partners?**
|
||||
A: Yes. Package the semantic views + Cortex policies as an app; partners can install it and use the chatbot without seeing raw data. Cortex Analyst can be seamlessly integrated into any application using REST API.
|
||||
|
||||
---
|
||||
|
||||
## Context
|
||||
|
||||
This case study was prepared as a technical exploration demonstrating governance-first semantic layer design for enterprise AI enablement. It reflects delivery patterns developed in a global industrial environment and adapted for privacy-safe public sharing.
|
||||
|
||||
Reference in New Issue
Block a user