Use Cases
Real problems. Real fixes. Real token counts.
🚀 Product Launch Coordination
The problem
Your marketing agent monitors social channels and draft posts. It sees internal chatter about v2.0 and, trying to be helpful, tweets "Just shipped v2.0! 🎉" — three days before the actual launch. The announcement goes out to 50K followers. Now your comms team is scrambling.
The edict
The result
Agent sees the edict before every action. The premature tweet never happens. On April 16, the edict auto-expires and the constraint lifts.
🛡️ Feature Existence Guardrails
The problem
A user asks your support agent "Does your product support gas sponsorship?" The agent, eager to help and pattern-matching from training data, replies "Yes, we support gas sponsorship for all transactions!" Your product has never had gas sponsorship. Now your support team has a promise to walk back.
The edict
The result
Agent checks edicts before responding. The false claim never gets made. Negative assertions are first-class citizens.
🤝 Multi-Agent Consistency
The problem
You have five cron agents: one monitors support tickets, one handles social media, one writes reports, one schedules meetings, and one manages releases. Each wakes up fresh with no shared context. Agent 1 says "v2.0 is live", Agent 3 says "v2.0 is in QA", Agent 5 says "v2.0 is planned for next quarter." Same product, five different realities.
The edict
The result
All five agents read the same edicts.yaml on every session. One source of truth, zero contradictions. Update once, propagate everywhere.
🔒 Compliance Constraints
The problem
Your company is in acquisition talks. A PR agent, asked about company strategy, mentions "exciting partnership discussions" in a blog draft. Or an agent responding to a community question casually references a project codename that's under NDA. These are career-ending mistakes.
The edict
The result
Compliance edicts are permanent and verified. Every agent, every session, every channel — the constraint is present before any output is generated.
⏱️ Time-Sensitive Operations
The problem
You're migrating your database. For the next 48 hours, agents should not trigger any write operations to the user table. After migration completes, this constraint should disappear. But someone always forgets to remove the manual override, and three weeks later agents are still refusing writes.
The edict
The result
Ephemeral edict with a 48-hour TTL. The constraint self-destructs when the migration window closes. No manual cleanup, no forgotten overrides.