Examples¶
Worked end-to-end use cases. Each one starts from a real-world problem a team is trying to solve, walks through the constitution and topology choices, and shows the receipts you'd expect to see in the audit log.
- Customer support with a refund cap — router, three L1 specialists, an L2 escalation. The simplest example: per-agent identity, capability-gated dispatch, live cap-revoke, self-revoke vs. operator-driven eviction. Layer a refund-cap constitution on top by following the patterns the next two examples use.
- Code review crew with security boundaries — reviewer + auto-fix + human-approver. A Cedar constitution forbids
patch_applied + security_sensitiveenvelopes; two bypass attempts trip the four-stage enforcement loop (detect → coach → quarantine → evict). Every change leaves a signed receipt. (LangGraph adapter.) - AP & invoice processing with payment caps — classifier, auto-approver, supervisor, treasury. Constitution gates over-cap authorizations on the presence of a
supervisor_approvedtag; the approver's bypass attempts trip the same enforcement chain. SOX-grade audit trail by default. (CrewAI adapter.) - Research crew with citation enforcement — researcher → fact-checker → editor connected by OpenAI Agents' handoff primitive. Constitution forbids
claim_publishedenvelopes that lackverified_citations; every handoff produces a Yutha audit envelope so the full agent collaboration chain is reconstructable from the receipt log. (OpenAI Agents adapter.) - DevOps incident-response with SRE countersign — alerting, triage, remediation, post_mortem, and a human SRE collaborate on a production-incident runbook. Constitution forbids
schema_changeproduction actions unless ansre_countersignedtag is present; bypass attempts trip the four-stage enforcement chain. (Microsoft Agent Framework adapter.) - Procurement platform with vendor isolation — buyer's LangGraph intake agent collaborating with three CrewAI vendor agents on a standing RFP platform. Bounded capabilities with
OnlyIfTaggedcaveats enforce a multi-party confidentiality wall between vendors; the constitution forbids cross-vendor data leakage; a bad-acting vendor walks the four-stage enforcement loop. (The first runnable heterogeneous-framework demo: LangGraph + CrewAI on the same swarm.)