Analysis

every engine, run against the real inputs

Peterson Technology PartnersAnsco & Associates · proof of concept
11 ENGINES · 4 ON REAL DOCUMENTS
RULE SETS: PROVISIONAL — PENDING AT&T SPEC

Every card below runs the actual engine against the actual inputs and prints what it printed — no recordings, no mock-ups. Where the inputs are synthetic they say so, and where an engine refuses to answer, the refusal is the output. The first group is the point: those answers come out of the close-out capture itself, with nothing extra collected.

the review desk → what the technician sees →
The wider operation

The questions Chris and dispatch asked for, and the format problem that sits between Ansco and every customer.

Fleet utilisation

“Does Chris need more trucks?”

synthetic data, real shape

Savannah carries three more than its work needs while Atlanta North is three short. A transfer, not a purchase.

~1s

Routing and dispatch

“What fits in the day, around the access windows?”

synthetic data, real shape

Exact search for the largest feasible set, and it names what will not fit rather than quietly dropping it.

~3s

The rule sets behind these are our best reading of AT&T’s requirements, not their published spec. Ansco’s own rejection history is what sets where the line actually falls — it calibrates the judgement, it does not create it.