Request classification and routing
I build automation that classifies each inbound request, plans bounded tasks, and holds high-risk tasks for approval; the dispatcher is in early access.
Try it
Paste an engineering request. The model classifies it into the dispatcher contract: kind, risk, estimates, the agent role it routes to, and whether it must wait for human approval. HIGH risk always requires approval, and output that breaks the contract is rejected.
Public demo on Cloudflare Workers AI. Inputs are screened by Llama Guard 3 before any other model runs, requests are rate limited, and nothing here connects to a Luca or customer system.
How it works
- Map the inbound flowI sample real requests with the team and agree on the labels, the required fields, and the route for each label. In Luca, an API caller submits a request through the intake app's authenticated POST /api/requests. That call requires the devops:requests:write capability and returns a request id that later stages use.
- Pin the output schemaI write the JSON contract first: intent, kind, risk, complexity, file and token estimates, suggested role, and approval flag. Regex patterns label the obvious requests, and the model is called only when no pattern matches.
- Validate the outputBefore routing, I check the model's answer: a risk other than LOW, MEDIUM, or HIGH becomes MEDIUM, and estimates are clamped to fixed ranges. If the model call fails or no model is reachable, the request falls back to medium risk with human approval required.
- Plan and routeThe dispatch loop picks up each new request, classifies it, and passes it to a planner that writes bounded task envelopes. Each envelope names the agent role, allowed and denied paths, required checks, and a file and line budget. A request that mentions a schema, a migration, or creating or altering a table splits into a schema task and a code task. The code task waits until the schema task is merged. Read-only questions close without opening any task. The planner uses keyword rules today, not a model.
Tools
| Tool | What it does here | Status |
|---|---|---|
| Agent dispatcher and plannerEarly access | Classifies each captured request by intent, kind, risk, and role, writes bounded task envelopes, and holds flagged tasks where workers cannot claim them. | Early access |
| Agent tool bridgeAvailable | Exposes database, event, and config services as agent tools, checks the caller's permissions first, and fails a call that runs past its time limit. | Available |
| CRM sales automation engineAvailable | Runs event-triggered workflows with conditional steps and template variables, and stores each step's result, error, and duration. | Available |
| Policy engine approvalsEarly access | Stores pending agent-action approvals with an expiry time and records who decided and when; the dispatcher uses its own approval route. | Early access |
| Demo classifier on Workers AIDemo only | Fills eight fields from the JSON contract my dispatcher's classifier asks its model for, in a public demo environment that calls no Luca system. | Demo only |
Available means shipped and in use. Early access means built but not generally available. Roadmap means designed, not built. Demo only means it powers the public demo, not customer deployments.
The write-up has every step of how I deliver this at a customer, with the tools and their status.
Read the write-up on gusit.deThe other answers
Built by Gus Assuncao of Gus IT LLC for a Forward Deployed Engineer application. Luca is the AI platform Gus IT builds and operates. Contact gus@gusit.de. Claude is a product of Anthropic PBC. Cloudflare and Workers AI are trademarks of Cloudflare, Inc. Llama is a trademark of Meta Platforms, Inc. Other names are trademarks of their respective owners. Gus IT LLC is an independent engineering firm and is not affiliated with or endorsed by these companies.