Specification Architecture · ABC I §3

Contract Catalog & Specification Guide

A behavioral contract transforms loose prompt guidelines into deterministic, auditable software boundaries. Explore 12 battle-tested YAML contracts across 8 enterprise verticals, enforcing preconditions, inline invariants (<10ms), governance gates, and recovery parameters.

Production Contracts

Enterprise Domains

100%

Hard Compliance

< 10 ms

Inline Latency

Runtime Execution Flow

The Contract Enforcement Lifecycle

Production Contract Catalog

Click any contract to view and copy its full production YAML specification.

finance financial-advisor.yaml

Wealth Management Advisor

Enforces SEC Rule 206(4)-1 disclaimer, blocks account balance exfiltration, checks KYC/AML preconditions, and enforces $5.00 session spend ceilings.

P 2

I 3

G 2

R Active

View YAML Specification ▼

agent: financial-advisor
version: "1.0"
domain: financial_services

before:
  - user must be authenticated
  - kyc_status must be "verified"
  - risk_profile must be initialized

during:
  - responses must not contain SSN or Tax ID patterns
  - responses must not contain raw credit card PAN numbers
  - session cost must stay under $5.00
    severity: critical
    action: block

after:
  - response must include standard SEC disclaimer
  - response must redact internal account routing identifiers

on_failure:
  retries: 3
  fallback: escalate_to_human
  message: "Routing session to certified human wealth advisor."

healthcare clinical-triage.yaml

Clinical Patient Triage

HIPAA Safe Harbor redaction on 18 PHI identifiers, emergency routing precondition, and medical disclaimer governance.

P 2

I 2

G 2

R Active

View YAML Specification ▼

agent: clinical-triage
version: "1.0"
domain: healthcare

before:
  - patient_consent must be true
  - jurisdiction must be within licensed state

during:
  - response must not contain unredacted PHI (HIPAA 18 Identifiers)
  - high_risk_symptom must trigger immediate 911 dispatch warning
    severity: critical
    action: block

after:
  - response must contain medical emergency disclaimer
  - triage level must be assigned (1-5 ESI scale)

on_failure:
  retries: 2
  fallback: emergency_phone_routing

codegen code-generator.yaml

Autonomous Code Generator

AST syntax validation, secret masking (API keys/private keys), banned library blocks, and cyclomatic complexity ceilings.

P 1

I 3

G 2

R Active

View YAML Specification ▼

agent: autonomous-coder
version: "1.0"
domain: devops_code

before:
  - repository_write_access must be true

during:
  - generated code must pass AST parsing without syntax errors
  - code must not contain hardcoded credentials or private keys
  - code must not invoke banned shell subprocess commands
    severity: critical
    action: block

after:
  - code must include automated unit test stubs
  - cyclomatic complexity must stay under 15

on_failure:
  retries: 3
  fallback: syntax_fix_agent

support customer-support.yaml

Enterprise Customer Support

Sentiment drift boundaries, refund authorization limits ($100 max autonomous), and SLA escalation triggers.

P 2

I 2

G 1

R Active

View YAML Specification ▼

agent: customer-support
version: "1.0"
domain: customer_service

before:
  - user_session must be active
  - rate_limit must be under 30 req/min

during:
  - refund_amount must stay under $100.00
    severity: critical
    action: block
  - sentiment_polarity must stay above -0.4

after:
  - response must log ticket id to CRM

on_failure:
  retries: 2
  fallback: escalate_to_tier2

legal legal-reviewer.yaml

Legal Contract Reviewer

Indemnity clause checks, GDPR data transfer validation, liability caps, and unauthorized practice of law disclaimers.

P 1

I 3

G 1

R Active

View YAML Specification ▼

agent: legal-reviewer
version: "1.0"
domain: legal_compliance

before:
  - document_hash must be signed

during:
  - review must flag uncapped liability clauses
  - review must flag missing GDPR standard contractual clauses
  - response must not give binding jurisdictional legal advice
    severity: critical
    action: block

after:
  - review must attach non-binding informational disclaimer

on_failure:
  retries: 2
  fallback: send_to_general_counsel

multiagent multiagent-handoff.yaml

Multi-Agent Handoff Pipeline

Contract enforcement across agent-to-agent delegator boundaries. Prevents shared co-failure and infinite loops.

P 2

I 2

G 2

R Active

View YAML Specification ▼

pipeline: multiagent-handoff
version: "1.0"
domain: compositional_orchestration

before:
  - upstream_agent_output must satisfy Schema_V1
  - maximum_hop_count must be under 5

during:
  - intermediate_token_drift must stay under D* = 0.27
  - handoff_payload must match downstream expected contract
    severity: critical
    action: block

after:
  - pipeline must record cryptographic execution certificate

on_failure:
  retries: 2
  fallback: swap_to_diverse_model_architecture