Know who you will break before you hit merge.

Implement contracts for data objects in your code.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form. Please try again.

Gable Understands Your Code

Code Editor

Contract

Impact Report

Gable — Data Contract & Impact Scan<\/span>
gable-bot commented · 2 minutes ago<\/span>

Summary:<\/span>
This PR modifies src/events/orderEvent.ts<\/span>. Gable compared the proposed
payload to contract contracts/orders/orders_v1.yaml<\/span> and found contract
violations and downstream impacts.

Violations (high severity)<\/span>
1. Breaking field rename<\/span> — orderId → id<\/span>
   Impact: consumers expecting orderId<\/span> (e.g., revenue_dashboard)

2. PII introduced<\/span> — customerEmail<\/span>
   Impact: asset forbids PII; introduces compliance violation.

3. Nullability change<\/span> — notes<\/span> nullable→non-null
   Impact: consumers relying on null semantics may break.

Downstream impact (detected consumers)<\/span>
• revenue_dashboard<\/span> — will break (uses orderId) — @bob-analytics
• order_ml_model<\/span> — model input mismatch — @ml-team
• orders_archive<\/span> — nullability mismatch — @data-platform

Status: Blocked — Gable check failed (contract violation)<\/span>

Code Editor

Contract

Impact Report

Gable — Data Contract & Impact Scan<\/span>
gable-bot commented · 2 minutes ago<\/span>

Summary:<\/span>
This PR modifies src/events/orderEvent.ts<\/span>. Gable compared the proposed
payload to contract contracts/orders/orders_v1.yaml<\/span> and found contract
violations and downstream impacts.

Violations (high severity)<\/span>
1. Breaking field rename<\/span> — orderId → id<\/span>
   Impact: consumers expecting orderId<\/span> (e.g., revenue_dashboard)

2. PII introduced<\/span> — customerEmail<\/span>
   Impact: asset forbids PII; introduces compliance violation.

3. Nullability change<\/span> — notes<\/span> nullable→non-null
   Impact: consumers relying on null semantics may break.

Downstream impact<\/span>
• revenue_dashboard<\/span> — will break (uses orderId)
• order_ml_model<\/span> — mismatch
• orders_archive<\/span> — nullability mismatch

Status: Blocked<\/span>

Shift-left data object contracts in your code

Block risky changes at PR time, see who’s affected, and roll out safely

Consumers don't know which object to use

Similar events/responses drift under different names and shapes. Teams pick the wrong one, duplicate work, and carry rework.

Changes lack impact context

Reviews miss breaking diffs. You can’t see which services, jobs, or pipelines will fail when a field changes or disappears.

Unknown owners and unclear communication

Who owns this code? Who made this change? Who needs to approve a change?

Solutions

Define what objects you ship before you build

Output catalog

Auto-surface every event/response your services emit so teams can see the canonical objects.

Contracts in repo

Enforce rules for each output, including fields, requiredness, and versioning, so unsafe changes are caught early.

See blast-radius in the pull request

PR Impact Map

Lists affected services, models, and jobs with the reason.

Suggested Reviewers

Auto-identify owners who should sign off.

Ship safely with clear guidance

Safe-Change Hints

Recommendations to version or scope changes to reduce impact.

Optional Merge Block

Hold merges until risk is addressed.

“I believe that Gable is the first next generation data management platform built for the AI era. It’s game changing for any company that truly values data and in this punch card generation of AI, I believe this is foundational.”

Kelvin Lim

Chief Technology Officer at x15ventures

“After putting Gable in production, we've had 0 data-related incidents.”

Zakariah Siyaji

Engineering Manager, Data Platform

Features

Contracts in Repo

Define object contracts alongside the service that emits them. Specify fields, requiredness, and semantics; generate docs for consumers; and enforce changes in CI so drift is caught before it ships.

PR Impact Map

Inline notes list the services, jobs, and pipelines affected by your change with the exact rule violated. You get a clear pre-merge view of blast radius and what to fix before you hit merge.

Suggested Reviewers

Automatically proposes the owners of the impacted code to request review from. Cuts ping-pong and shortens approval time.

Safe-Change Hints

Guidance to version, gate, or scope your change to contain risk. Suggestions are informed by patterns from similar merges that landed safely.

Read our featured Articles

Blog Article

The Shift Left Data Manifesto

A core idea behind shifting Data Left is simple but often overlooked: data is code. Or more accurately—data is produced by code. It’s not just some downstream artifact that lives in tables and gets piped into dashboards and spreadsheets. Every record, event, or log starts somewhere—created, updated, or deleted by a line of code. And just like DevOps demonstrated, if you want to manage something well, you start at the point of creation.

Chad Sanderson

March 25, 2025

Data governance

Automated Data Governance: The Science of Better Compliance

Despite all the upsides, the prospect of automated data governance can be daunting. For good reason. However, data contracts can make all the difference here.

Chad Sanderson

August 1, 2024

Data governance

3 Data Contract Types and Examples

Understanding the concept of data contracts is important. But the right data contract examples demonstrate how important they are in practice.

Chad Sanderson

November 5, 2024