Atlas Proofing Pipeline
Every page of a mailer checked against the merchant list before it prints, with a person signing off.
Innovation & Strategy Analyst · inventor of Atlas · Jan 2026 → present · in use
Print proofing was a person checking every page by eye, every version of every job. Now the pass runs when the PDF lands, and the person signs off on what it flags.
In sixty seconds
Every page of a mailer checked against the merchant list before it prints, with a person signing off.
- was
- Someone checked every mailer page against the merchant list by eye.
- now
- A model reads every page against the merchant grid; a person signs what it flags.
- the decision
- Instrument the hours before claiming the dollars, and keep a person at the gate.
- the run
- Print Proofer demo →
- where it sits
- the map →
Opened · The mailer
A retail mailer, a grid of merchants, and a person checking every page by eye.
A print mailer comes in with its pages and a merchant grid: every logo, offer and legal line that has to appear, on the right page, before it goes to print. Someone at the agency sits with the PDF and the grid and checks them against each other. It happens with every version of every job, and the mistakes that slip through are the expensive kind.
Nobody enjoyed that pass, and nobody could skip it.
Blocked · The cost
Human attention, every version of every job, on a pass a machine can run.
Proofing was the invisible time sink of the creative team: human attention on a low-signal pass, repeated for every version of every asset.
How many hours it took, and how many it gives back, are numbers I will publish with their receipts, not before.
The pass was mechanical. That is what made it automatable.
Reassigned · The decision
Automate the low-signal pass first. Keep a person at the gate.
Inside Atlas I built a vision-model pass that reads each page and matches what it finds against the merchant grid, with fuzzy matching for the ways a logo or a name gets mangled in print. The constraint: it had to run on the proofs the team already submits, not in a separate app anyone has to remember. The rule: a person signs off before print, every time.
What I did not do
- Letting the model sign off
- Anything under a confidence line goes to a person, and a person signs every proof.A person stays in the loop on every job.
- Exact string matching against the grid
- Print misspells and abbreviates. A matcher resolves them by character similarity plus the logo, so only the real misses reach a person.The pass is only as good as the grid it is given.
- Claiming the hours, or the dollars
- Instrument the hours before claiming anything.The page carries no hours and no dollar figure until both are counted and attested.
The first pass caught what the eye had been missing.
In progress · How it runs
Page 1 of 8 read against the merchant grid, 0 for a person.
the grid · Northeast · Week 03 · Jan 20
- Orchard Subs
- Harbor Grill
- Summit Burger
for a person0
- Nothing yet.
Scripted simulation on an invented mailer. Its pages and verdicts belong to the fixture.
Every page read, every merchant matched, every miss flagged for a person.
The run beside this simulates the pass: each page scanned, each merchant found or flagged, and an issue log for the person at the gate.
One decisionChain-of-verification prompting plus fuzzy matching, so ambiguities resolve automatically and only the real misses reach a person. The trade: the pass is only as good as the grid it is given, so the grid is versioned with the job.
When it breaks
- The model is unsure about a page
- the system Under the confidence line the page goes to a person instead of being marked clean.
- seen by The proofer who signs
- A merchant on the grid is on no page
- the system It is flagged missing, with the grid week it came from.
- seen by A person, before print
- A merchant on a page is not on the grid
- the system It is flagged unexpected, and a likely swap from another region is named as such.
- seen by A person, before print
Then the hours had to be counted, not estimated.
Closed · The change
A pass by eye, then. A pass that runs when the PDF lands, now, with a person signing what it flags.
Proofing has run through Atlas since January 2026. The pass runs when the PDF lands, on the same jobs with the same grid, and the creative team reads what it flags instead of reading every page.
How many hours that gives back is a number this page does not carry until it has been counted; I will publish the count with its receipt, or not at all.
A week nowThe proof runs when the PDF lands; the creative team spends the day on the creative.
The pass by eye, handed to the machine; the signature, kept.
Next
Do again
Instrument the hours before claiming the dollars, and keep a person at the gate.
The same shape as the auditor: the human checklist, encoded, with a person signing off. I am looking for an applied-AI engineering role at a company with operations like these to automate.
Ask me about
- What does the pass do when the vision model is unsure about a page?
- Anything under the confidence line goes to a person instead of being marked clean, and a person signs every proof. The model never gets to decide alone.
- Why no hours on this page?
- Because they have not been counted. The number comes back with its receipt, or not at all.
Built with
Hire me
I'd build this for your team.
I am looking for an applied-AI engineering role at a company with real operations to automate. The résumé is one page.