The shape of a readable rule.
Every rule should name a signal, a condition, an action, and an accountable person. The static demo stores descriptions of these rules; it does not execute a workflow engine.
| Part | Meaning | Example |
|---|---|---|
| Signal | What begins a run | Signed contract ready |
| Condition | What must be true | Required contact details are present |
| Action | What the next owner does | Review and propose kickoff |
| Accountability | Who handles uncertainty | Avery Chen, with Jules as backup |
Design the exception before the shortcut.
Missing information should have a destination. Write the manual review path before you automate the normal one. A silent failure is an ownership problem as much as a technical problem.
- Distinguish a temporary failure from an invalid input.
- Keep the original request and show the last known state.
- Avoid automatic retries for metered AI requests that might already have consumed quota.
- Require a human decision before rejecting a customer or sending an external message.
The two live tools.
Both tools use assets/js/ai/core.js unchanged. The trusted download flow replaces
the token-free config.js with your account’s authorized development configuration.
Frontend credentials are inspectable, and usage shares your account’s quotas.
Smart Routing AI Model
Action chat sends a non-streaming chat request. The core helper uses model
smart-route-mini and reads choices[0].message.content.
POST /api/smart-routing-ai-model/v1/chat/completions
{
"model": "smart-route-mini",
"messages": [{"role": "user", "content": "Draft a review workflow."}],
"stream": false
}Try the workflow drafting form →
Email Validator
Action check-email sends a GET request with the email query field. The
page displays the returned response without inventing an interpretation of undocumented fields.
GET /api/email-validator/v1/check-email?email=hello%40example.comAccess, errors, and quotas.
Preview access displays the account-download instruction. The supplied client disables duplicate submissions, shows loading status, supports cancellation, and renders real errors and returned quota data. A 429 response offers the relevant plan link. A network failure allows an explicit retry.
Production integrations should keep credentials in a secure backend, enforce authorization and rate limits, validate input, and record actual outcomes. The static template makes none of those server-side guarantees.