Second Brain

Encode "budget pools are separate — never conflate or sum across" as a permanent feedback memory + MEMORY.md pointer + cost-section corrections to the snowflake-cortex-routing-agent SKILL.md and READM

1 min read

Encode “budget pools are separate — never conflate or sum across” as a permanent feedback memory + MEMORY.md pointer + cost-section corrections to the snowflake-cortex-routing-agent SKILL.md and READM

Decision

Encode “budget pools are separate — never conflate or sum across” as a permanent feedback memory + MEMORY.md pointer + cost-section corrections to the snowflake-cortex-routing-agent SKILL.md and README.md.

Rationale

AJ corrected mid-session: I attributed Snowflake routing-agent costs to the AWS Runwal AI Forge ₹1L/mo Tier 1 budget. These are contractually distinct billing pools (Snowflake enterprise agreement vs AWS Workmates reseller invoice). Conflating them makes cost estimates meaningless and misroutes governance decisions. Saved feedback_budget_pools_separate.md (22 lines, in budget) with the rule + Why + How to apply; added one-line pointer in MEMORY.md (167 lines, within 170 target); rewrote cost sections in SKILL.md (now: Snowflake credits only, with explicit pool-separation disclaimer + METERING_HISTORY observability hook) and README.md. Future cost estimates must identify the pool first, estimate in pool-native unit, and never sum across pools. This is permanent behavioral guidance that prevents the lapse from repeating across all future deployments and skill creations.

Alternatives Rejected

Outcome

Pending

Graph View

Backlinks