vantage-snowflake-only-single-source-architecture
Runwal Vantage consumes only Snowflake as its data source. All upstream sources (Salesforce, SAP S/4, SharePoint CSV/Excel) are pre-materialized into Snowflake via Fivetran/n8n/custom shims before Vantage touches them. Zero ingestion, polling, or file parsing code lives inside Vantage — this is AR-4 (absolute anti-requirement). Building any file-ingest or API-pull connector inside Vantage violates the architecture boundary.
Related
- runwal-vantage-project-scope-canonical-reference
- nova-decision-log-consolidated
- clawteam-openclaw-multi-agent-swarm-evaluation
- rbac-rls-at-query-execution-layer-is-non-negotiable-enterpri
- rls-at-query-execution-layer-enterprise-bi-non-negotiable
- redash-query-runner-extensibility-hook
- sharepoint-data-must-flow-through-snowflake-not-vantage-inge
- bi-platform-single-source-principle-all-via-snowflake
- r-dash-single-snowflake-connector-zero-ingestion
- r-same-snowflake-only-no-ingestion-architecture
- r-same-snowflake-only-no-direct-source-connectors
- r-same-snowflake-only-consumption-zero-ingestion
- sharepoint-snowflake-no-ingestion-in-analytics-platform
- sharepoint-must-materialize-to-snowflake-upstream
- r-same-all-data-sources-funnel-through-snowflake-only
- r-same-snowflake-only-consumption-ar4-constraint
- sharepoint-sap-salesforce-all-via-snowflake-zero-ingestion
- sharepoint-data-routes-through-snowflake-vantage-is-consumpt
- sharepoint-data-flows-via-snowflake-not-direct-ingestion
- r-same-sharepoint-snowflake-upstream-only