三 agent 分工，Jev 当发票与合同的判定闸门

octarinx @octarinx原推发布于 2026.10.14

在 X 上打开原推

I SOLD A SYSTEM MY AGENTS BUILT FOR $115,000. IT ONLY READS FILES THE CLIENT ALREADY HAD a distributor asked me one boring question: are our suppliers billing what they agreed to the answer was already on their drives. 41 supplier contracts, 3 years of invoices, 18,406 lines. nobody had ever put the two side by side, because it's the most boring reading in any company and boring reading is exactly what got cheap worldcc says procurement contracts lose ~11% of their value after they're signed. part of that is plain overbilling: price changes nobody tracked, discounts nobody applied so i gave the build to three agents and wrote down what each of them is not allowed to do haiku 5.5, the clerk. reads every contract and every invoice line and turns them into clean rows: prices, escalators, volume discounts, end dates. never judges anything jev, the gate. matches each invoice line to its contract term and says pass, flag or skip. thousands of tiny decisions, zero prose. only flags move up opus 5.5, the architect. designs the system, writes the code and the tests, and for every flag writes a note a cfo can forward to the vendor. never sees a line jev passed the trick is who does the reading. haiku reads at $0.10 per million tokens, opus at $4. that 40x is the only reason reading 3 years of invoices made sense 46 hours later it ran on last quarter. their own files, their own vendors nobody haggles over the price of a system that just showed them their own money walking out the door the prompts: 1. haiku 5.5 — the clerk "you are a clerk, not an analyst. read every file in contracts/ and write terms.jsonl: vendor, item, agreed unit price, price escalator (rate and date), volume discounts with thresholds, payment terms, contract end date. then read every file in invoices/ and write lines.jsonl: vendor, invoice number, date, item, quantity, unit price billed, total. copy every number exactly. if something is unreadable write 'unknown'. no opinions" 2. jev — the gate "match every row in lines.jsonl to its term in terms.jsonl. for each line return pass, flag or skip. flag if: r1 the billed price is above the agreed price after escalators, r2 a volume discount should have applied and didn't, r3 the invoice repeats lines from another invoice, r4 the contract had already ended. skip if there is no matching term. write verdicts.jsonl with the rule that fired. never write prose, never change a number" 3. opus 5.5 — the architect "build this as a system the client runs every month: one script that runs the clerk and the gate on new files, tests that prove each rule r1-r4, and a dashboard of flags by vendor with the money at stake. then, for every flag in verdicts.jsonl, write a short note a cfo can forward to the vendor: what the contract says, what was billed, the difference, with page and invoice references. you only see flagged lines" the expensive part was never the reading. it was that nobody had done it

这条是引用着另一条写的：x.com/xinc3s/status/2108204467774509059