The chemical washout check

The check that runs before a chemical load is tendered.

A tank's last wash, its last three loads, and the rules that govern what may follow them — read together, decided by rules only, and written into a record that never rewrites itself. Not at the gate. Not after the fact. Before the tender.

See how the check works Watch the evaluation walk

ChemCheck is built and is being evaluated with partners. This page says only what is true of it tonight.

The walk

One load, end to end.

The same walk our evaluation partners take: a certificate becomes a record, the record meets the chain and the rules, the check answers, and the answer becomes a proof a facility can open.

Record → Chain → Verdict → Proof — the driver app and the office console, in that order.

The system

Four parts. One verdict.

Each part does one job and keeps its own evidence, so when the check answers, it can show its work — the record it read, the chain it read, and the rule that decided.

PART 1 — THE RECORD

Born from the certificate photo

A wash record starts the way the proof starts: the driver photographs the cleaning certificate. The four fields are read off that photo, the wash time is entered as it stands on the paper, and the seals on each opening are recorded with it.

The record then carries a standing — awaiting first use, recorded, window passed, or replaced by a newer wash. Records are replaced, never deleted: a newer wash supersedes the old one, and the old one stays on the record as history.

PART 2 — THE CHAIN

The last three loads, read honestly

Every completed load appends to the equipment's product chain — in specific product names, never in vague ones. The check reads the last three.

A load nobody named stands in the read as an unknown stretch — it never quietly becomes a known product.
A gap in the history reads history unknown, a first-class answer — and a check never clears over a gap.
A correction is a new entry that supersedes the one it corrects. The chain itself is never edited.

PART 3 — THE RULES

Rules with sources, in five layers

Every rule in the base carries its source, and the layers resolve in a fixed order — the layer above wins:

Shipper matrixYOUR SHIPPERS
CompanyYOUR POLICY
StateWHERE IT RUNS
IndustryTHE PRACTICE
Federal floorTHE LAW UNDERNEATH

A shipper's matrix enters only as a version — numbered, dated, attributed, a source on every rule — never as a quiet edit. And silence is never read as a clear: where no rule speaks to a pairing, the check escalates instead of waving it through.

PART 4 — THE CHECK

Decided by rules. Kept in a ledger.

The check reads the current record, the chain, and the rules that apply — and answers in the verdict words below. No model decides. No person overrides quietly. A blocked verdict is final on every surface.

Every check appends one entry to the verdict ledger: the verdict, the rule that decided it with its source, the chain and record as they stood at that moment, who ran it, and when. The ledger has no edit and no delete — a verdict can be answered by a later check, never rewritten by one.

The proof a facility can open

A clear verdict mints a QR proof the driver carries on the phone. A facility opens it with no sign-in and sees exactly the cleared slice: the carrier, the equipment, the last three loads in specific names, the most recent wash with its seal numbers, and the verdict in its own words. A wash-required or blocked verdict mints nothing — there is no code to wave at a gate. If the standing changes after the mint, the old code says so in plain words instead of silently pointing at a clear that no longer stands.

The verdict words

Three answers. Said exactly the same way, every time.

The check has three answers, and they are the product's own words — on the driver's phone, in the office console, and on the proof page, word for word.

Cleared

“Cleared to tender, subject to plant inspection.”

The record is current, the chain is known, and no rule stands against the pairing. The words carry their own honesty: every shipper reserves its gate inspection, so a clear is a clear to tender — never a promise about the gate.

The cure: none needed. The load can be tendered.

Wash required

“Wash required” — with the level named.

The pairing may follow, but not on the wash of record: the sequence, a gap in the chain, an incomplete photo set, or silence in the rules calls for a named cleaning level first — up to a full wash plus inspection where the rules are silent.

The cure: the wash the verdict names. A new certificate is photographed, a new record is born, and the check runs again on fresh paper.

Blocked

“Blocked.”

Some loads can never follow each other — a chemical history into food or feed, a reactive pairing. A hard-block rule has spoken, and its source rides with the verdict so the office can see exactly why.

The cure: there is no wash cure. No cleaning level makes a blocked pairing lawful — the answer is different equipment.

Cora

She teaches. The check decides.

Cora is the voice in the driver app — a guide who answers from the same knowledge base the app itself shows, so what she teaches and what the screens teach are the same words. She can explain the certificate, the chain, the layers, and what a verdict means, in the cab, hands-free.

Ask her for a verdict and she will tell you the truth about her own job:

“That is guidance from the standard — it is not a verdict. The check has to run before this load is decided.”

Why the line is drawn there

A verdict is a record. It goes in the ledger with the rule that decided it. A voice cannot carry that, so a voice never renders one.
She teaches from the open book. Her knowledge base is the product's own teaching — the same sections a driver can read in the app.
She knows her limits out loud. An unknown product name escalates; it never gets guessed into a clear — by her, or by the check.

Evaluation

In evaluation with partners now.

ChemCheck is built — the record, the chain, the layered rules, the check, the ledger, the proof, the driver app, and the office console — and it is being evaluated with partners before it is offered any wider. An evaluation runs on your world, not a demo world:

What an evaluation covers

Your equipment — DOT 407, DOT 412, DOT 406, ISO tanks, dry bulk pneumatic, with partial coverage named honestly where it is partial.
Your shippers' matrices, loaded as governed versions — numbered, dated, attributed — never as quiet edits.
Your drivers, their standings, and the one-time rules test with our own certificate — stated as ours, never dressed as a state or federal one.
The full record, open to your engineers and your security review: the system is built to be pulled apart and checked.

What we will not claim

No customers we cannot name and no results that are not ours to state.
No certification language the product has not earned.
Last-three is shipper practice, not a federal rule — we will never sell it to you as a legal requirement.
A clear is a clear to tender, subject to plant inspection — the gate always has its say.

To talk about an evaluation for your fleet, start on the support page — during the evaluation period, that is where the conversation begins.