contracts

DE//AGENT currently lists 10 resources under contracts: 4 tutorials, 1 skill, 1 plugin. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Also present: 1 hook, 1 agent, 1 runbook, 1 pattern.

Documented learning objectives across these resources:

• Apply backward/forward compatibility rules to a diff — via Schema Change Contract Review
• Detect a breaking change hidden behind a "safe" rename — via Schema Change Contract Review
• Write a deprecation plan with dates — via Schema Change Contract Review
• Configure a pre-commit check over staged schema files — via Enforce contracts in CI with the schema change check
• State what lets a breaking change pass — MIGRATION.md or a deprecated_at annotation — via Enforce contracts in CI with the schema change check
• Explain why the gate belongs in the producer's CI, not the consumer's runtime — via Enforce contracts in CI with the schema change check
• Classify a breach by clause — schema, semantics, or SLA — via Respond when a data contract breaks
• Bound the consumer impact set from lineage before assigning the fix — via Respond when a data contract breaks

7 more objectives live on the individual resource pages.

These resources map to stage: Data Quality (10). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. Schema Change Contract Review score 40.5 — intermediate
2. Schema drift score 34.75 — intermediate
3. Contracts as a Quality Gate score 34.75 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: Enforce contracts in CI with the schema change check.

Security-flagged entries: Schema Change Contract Review (1 flag), Schema drift (2 flags), Contract Kit (2 flags), Schema Reviewer (1 flag), Schema Change Check (2 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

Known limits: A single team owning the whole chain (Contracts as a Quality Gate)

• Schema Change Contract Review — Diffs an old and new schema, classifies the change (compatible / risky / breaking) against consumers, and produces the migration and comms plan. details
• Enforce contracts in CI with the schema change check — Install the Schema Change Check as a pre-commit gate over staged schema files so a breaking change exits non-zero unless a migration plan or deprecation annotation rides along with… details
• Respond when a data contract breaks — Work the broken-contract runbook end to end: identify which clause broke, bound the consumer impact set from lineage before anything else, decide whether the producer reverts or th… details
• Review a schema change against its contract — Run the Schema Reviewer's four-step pass over a producer's schema diff — classify each field change, resolve consumers from lineage, emit a dated migration plan — and use the schem… details

Real install commands from the registry — read the source before running any of them:

npx de-agent-platform add schema-change-contract-review

Schema Change Contract Review — review first

amp plugin add de-agent/contract-kit

Contract Kit — review first

Adjacent topics: tutorial (4 shared), schema (4 shared), ci (3 shared), hook (2 shared), guardrail (2 shared), migration (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.