Second Brain

Build G2 Cost Pre-Flight as Runwal-local guardrail inside fivetran-mcp…

2 min read

Build G2 Cost Pre-Flight as Runwal-local guardrail inside fivetran-mcp…

Decision

Build G2 Cost Pre-Flight as Runwal-local guardrail inside fivetran-mcp, diverging from upstream Bible framework v19.1.3 which REMOVED G2. Remap scope doc’s database/schema/column references from aj-ea’s assumed RUNWAL_SNOWFLAKE_PROD.FIVETRAN_METADATA single-schema Platform Connector layout to the live RNWL_RAW.{FIVETRAN_METADATA, FIVETRAN_METADATA_FIVETRAN_PLATFORM} dual-schema reality discovered in Phase 1.0 pre-flight. Pause before Phase 1 DDL execution for explicit AJ authorization on production Snowflake modification.

Rationale

Phase 1.0 live-state probe via snowflake MCP caught 6 drifts from scope: (1) database RUNWAL_SNOWFLAKE_PROD does not exist — actual is RNWL_RAW; (2) Fivetran metadata is split across two coexisting schemas not one; (3) 4 of 6 target tables are named differently in the Platform Connector’s dbt-transformed layer (FIVETRAN_PLATFORM__* prefix); (4) column names diverge — MEASURED_DATE not measured_timestamp, CONNECTION_NAME not connector_id, requires CONNECTION table join; (5) rows_in_source_table column used in scope § 7.2 does not exist — must use MAX(TOTAL_MONTHLY_ACTIVE_ROWS) over 12mo as confidence=medium proxy; (6) mar_tier column does not exist — Fivetran migrated to flat-rate per-destination pricing. Upstream framework removal signal (contract_enforcer.py:17, contract.yaml:148-153, SKILL.md:258) was invisible to aj-ea when scope was drafted; AJ resolved in-session with explicit Runwal-local divergence directive. Scope § 6.1 DDL would have failed at first GRANT statement if executed verbatim. Live data validated scope’s Salesforce sanity-check ranges (46k rows/day sits inside 10k-500k) and surfaced a stronger G2 target: SAP HANA at 3.3M/30d (2.4x Salesforce). Pausing for AJ go-ahead before provisioning role/user/warehouse in production Snowflake respects auto-mode rule 5 (production modification needs explicit confirmation) and feedback_autonomous_by_default carve-out (strategic + irreversible boundary). 0.85

Alternatives Rejected

Outcome

Pending

Graph View

Backlinks