What problem does it solve? Deciding where a new data source, system, or dbt model should be materialized in the SIAN platform is an architectural decision with direct cost impact, since gcp-sian-dados shares costs across all group companies. This Skill removes ambiguity by applying a clear shared-versus-exclusive criterion and showing exactly how to configure the dbt project accordingly. ## Core Features & Use Cases - Destination Decision Criteria: Classifies a system as shared (multi-company, goes to gcp-sian-dados) or exclusive (single company, goes to gcp-sian-proj-<empresa>), with concrete examples like Protheus, RM, Pontotel, and MIX. - dbt Configuration Guidance: Provides ready-to-adapt dbt_project.yml snippets for both shared models under models/sian/<sistema>/ and exclusive models under models/clients/<empresa>/, including schema and materialization settings. - Governance Rules: Enforces that the destination decision is declared in the PR, that Raw ingestion tables always land in gcp-sian-dados.raw, and that exclusive data is exposed only via RBAC on the company project. - Use Case: When adding the MIX system for Urbi, the Skill identifies it as company-exclusive, directs the models to models/clients/urbi/mix/, and configures +database: gcp-sian-proj-urbi. ## Quick Start Ask the assistant to determine where a new system or dbt model should be materialized in the SIAN platform and how to configure it in dbt_project.yml.
