Schema Evolution And Contract Migrations

Overview

Use this skill when a schema change can ripple through pipelines, models, dashboards, or external consumers. It helps agents make schema evolution deliberate, compatible, and recoverable.

When to Use

• changing input or output schemas
• renaming or dropping columns
• changing data types or nullability
• adding keys or changing grain
• migrating consumers from an old contract to a new one

Do not treat schema changes as isolated SQL edits. They are compatibility events.

Workflow