Manufacturing · The Friday line-down
A three-day, four-person question, answered in minutes
An agent that reads the contracts, service levels, and open orders you already have, shows its working as auditable tool calls, and cites the clause behind every claim.
- To answer the breach question by hand
- 3 days
- Pulled in to chase the answer
- 4 people
- With the agent on your contracts and orders
- Minutes
- Cited to the clause and the ERP rows
- Every claim
01
The problem
This is a scenario rather than a named engagement: the walkthrough we use to show how agent builds run. The question is real in every plant we've sat in.
A line goes down on Friday, and “which contracts do we breach?” takes three days and four people to answer. The contracts, the service levels, and the open orders all exist. They just live in different places, and nobody reads them together until it's urgent.
02
The approach
The system reads the contracts, service levels, and open orders you already have, and works the question the way a person would: which SKUs the line feeds, what each contract commits to, which orders are already scheduled this week.
Every step shows as a tool call you can audit. Nothing is a black box; the reasoning is on the screen, next to the sources it pulled from.
03
The outcome
The answer comes back in minutes, and every claim cites the clause and the ERP rows behind it.
A person signs off before anything leaves the building. The agent does the reading; the decision stays with the people accountable for it.
The question this answers
If packaging line 2 is down until Friday, which customer contracts do we breach?
The system
Worked scenario · The Friday line-down
Ask the operation anything, with citations
Language models put your documents on call: contracts, claims, tickets, maintenance histories. Retrieval keeps every answer grounded in the source, and a person signs off where it matters.
You
If packaging line 2 is down until Friday, which customer contracts do we breach?
thinking · Line 2 feeds three SKUs. Check committed service levels per contract, then orders already scheduled this week.
affected_orders(line: "pkg-2", until: "fri")→ 3 SKUs · 11 open orders · 4 due this week.
service_levels(skus: ["405", "417", "442"])→ Two contracts at 98% OTIF · one 48-hour cure window.
breach_exposure(orders: […])→ 2 orders breach Thursday · penalty cap €40k · notice due 24h ahead.
Gatsby agent
Two orders breach Thursday — both under the Meridian contract. Notice is due by
Every answer cites the clause and the ERP rows it came from.
More of the work
The next one is scoped from your diagnostic.
Every build starts with the same two weeks inside your operation. Tell us what's slow.