Domain Contracts
Contracts
12 YAML behavioral contracts across 8 enterprise domains. Hard and soft constraints for production AI agents.
Contract Catalog
Each contract defines preconditions, invariants, guarantees, and recovery strategies using the ABC framework.
Contract Details
Hard constraints are enforced strictly. Soft constraints allow drift within defined bounds.
| Domain | Contracts | Hard | Soft | Focus |
|---|---|---|---|---|
| E-Commerce | 3 | 18 | 12 | Order processing, inventory, pricing |
| Finance | 1 | 8 | 5 | Transaction compliance, risk assessment |
| Healthcare | 1 | 7 | 4 | Medical triage, patient safety |
| Retail | 1 | 6 | 4 | Returns, support, recommendations |
| Telecom | 1 | 5 | 3 | Billing, provisioning, SLA |
| Dev Tools | 1 | 6 | 4 | Code generation, review, CI/CD |
| Research | 1 | 4 | 3 | Literature search, summarization |
| General / MCP / RAG | 3 | 14 | 9 | Cross-domain, tool calling, retrieval |
Contract Structure
Every contract follows the ABC = {P, I, G, R} four-component structure.
P — Preconditions
Input constraints and environmental requirements that must be satisfied before agent execution begins.
I — Invariants
Properties that must hold throughout execution. Violations trigger immediate recovery actions.
G — Guarantees
Output conditions and behavioral bounds that the agent must satisfy upon completion.
R — Recovery
Drift detection and correction strategies applied when behavioral bounds are exceeded.
Explore Contracts
Full contract source code is available on GitHub.