Design a Manufacturing Operations Agent
Design a grounded assistant that reports production progress, opens work orders, and prepares customer quotes with safe permissions.
Problem statement
For this exercise, assume an authenticated employee asks a manufacturing agent to check production progress, open a work order, or prepare a quote for a customer. Production, work-order, customer, and approved pricing facts live in existing systems of record.
The agent must identify the relevant record, report its source and freshness, and ask for clarification or say that a fact is unavailable when the record cannot support an answer.
It may draft a work order or quote, but a permitted employee must confirm the exact proposed action before a work order is created or a quote is sent. Quote amounts come from approved pricing rules rather than model-generated numbers.
Operations staff may create work orders for their assigned plant; sales staff may prepare and send quotes only for their assigned customers. A customer cannot use the employee agent.
Design the agent, its tool and data boundaries, the production-progress read path, the work-order and quote paths, hallucination controls, and authorization. Assume one manufacturer and one deployment region.
Replacing the production scheduler or pricing system, inventory reservation, payment, and customer-facing chat are outside scope.
What to build
- An authorized employee can ask for a production order's progress and receive a grounded status with record identity and freshness, or an explicit unavailable or clarification outcome.
- An authorized operations employee can review and confirm a proposed work order for an assigned plant and retrieve its durable creation outcome after retries.
- An authorized sales employee can review a quote calculated from approved pricing data, explicitly confirm delivery to an assigned customer, and retrieve the sent quote and its validity.
- Every read and action is scoped to the employee's current permissions; unsupported facts and unapproved actions never become completed answers or writes.
At scalePractice assumption
- 50 agent requests per second at peak across 500 active employees; work-order creations and quote sends are each under five requests per second.
- Progress responses target five seconds at p95 and must show a source timestamp no more than 60 seconds old or explicitly say that the progress is stale or unavailable.
- A quote pins an approved price-rule version and expires after 15 minutes; expired quotes must be recalculated and reconfirmed before sending.
- Once an employee confirms a work-order creation or quote send, retries must not create a second work order or send a second quote; an uncertain external outcome remains pending until reconciled.