Corobate
Walkthrough · the real engine runs in this page
1 · The problem
2 · Set the rules
3 · Collect
4 · The decision
5 · Six readers
6 · Try to forge it

Build a receipt, in six steps

Step 1 of 6

You already wrote the receiving standard. Can you prove it was followed?

Not the standard — you can produce that. This shipment. What your rule required for it, what was actually collected against that rule, and, if something was missing, who released the goods anyway and what they were looking at when they did.

Most teams can show the first half and not the second. The standard is a document. What happened on the dock at six in the morning, with a truck waiting and a form that did not quite match, is an email thread — and you find out which one won at the audit, six months later.

A refusal is not a stop. It is a date. The gap was always there. The only thing that changes is when you find it.
Where the gap surfacesWhat it costs
At the dock, named, with the supplier on the hookAn hour and one email
At your customer's incoming inspectionA return and a corrective action
In an audit, or at a borderA finding, a hold, sometimes a recall

Over the next four minutes you will play two people. First the supply-chain manager who writes the standard — that is you, and they are your rules, not ours. Then the receiving clerk who has to work with whatever is actually on file. Then you will watch your own rule refuse your own shipment, see what six different people are shown about it, and try to fake the record.

This is not a video and it is not a mock-up. The engine that ships to a server is running in this page, and the verification harness checks the two builds against each other decision by decision. When you press a button a real decision is made and a real record is sealed. Nothing leaves your browser and nothing is stored.
Step 2 of 6

You are the supply-chain manager

Your job hereDecide what must be collected before goods can be received, how strong the evidence has to be, and how recent. You are writing an instrument, and it will be signed under your name and checked against your role before it takes effect.

A dial per question, and no free text anywhere. Move one and read the sentence under it — you do not need to learn the vocabulary first. You cannot write logic here, you cannot weight one claim against another, and you cannot make the test easier to pass: every setting available can only ever make it harder. That is what makes it safe to hand you the controls.

You will notice the receipt comes back carrying one dial you were never shown — where this claim stands on evidence a model wrote about itself. That is deliberate, and it is the point of the next paragraph rather than an oversight here.

Set them where your standard actually sits today, not where you wish it sat. The interesting number is how much of what you already receive would fail it.

What is at stake

the exposure selects the threshold tier — it is never defaulted

Try it twice. The same evidence that clears a $5,000 consignment will not clear a $250,000 one, because a supplier's own word caps at 50% and the bar for material exposure sits above it.

Step 3 of 6

You are the receiving clerk

Your job hereThe form below was produced by the rules you just set — you did not design it and you cannot add to it. Select what is actually on file. There is no free-text box, because a free-text box is where a control goes to die.
Notice what the form does not ask you. It does not ask whether you think the evidence is good enough — that was decided upstream, by someone entitled to decide it, and recorded. Your job is to say truthfully what you hold.
Step 4 of 6

The decision, and the record of it

This ran just now, in your browser, on the criteria you set and the evidence you selected.

The dials, read back off the sealed receipt

These are the settings the decision actually ran under. They are not read from the form you filled in — they are re-derived from the regulatory bindings inside the receipt's hashed body, so a receipt whose bindings were altered draws different dials.

The grey dial is the one worth your attention. You set five. The receipt carries six, and the sixth — whether a model's own output may carry this claim — is grey because nobody set it. It admitted model-written evidence, capped at MODELED as any model output is, because that is this deployment's default and no authority in force had taken a position. That is a setting, not an absence, and the receipt says so in those words. It is grey rather than absent for a reason a compliance officer will recognise: in a year's time, when someone asks whether your controls admitted AI-written evidence, "the regulation allowed it" and "nobody had thought about it yet" are very different answers, and a receipt that could not tell them apart would be answering neither.
The confidence is the minimum over the required claims, not an average. A weighted average would let three strong documents cover for one missing one, and the question was never "does the evidence look fine on average" — it was "did we know each necessary thing well enough".
Step 5 of 6

Six people, one decision, six different documents

The receipt above is the complete record, and that completeness is exactly why it cannot be handed to everybody. Each copy below was derived from your sealed decision by the engine, and each carries its own digest — which the sealed receipt committed to before any of them existed.

Step 6 of 6

Now try to forge it

You wrote a receiving standard four minutes ago and watched it hold.

The interesting number is not on this page. It is how much of what you received last quarter your own standard would have stopped. That runs against your files, in shadow — nothing enforced, nothing blocked, one lane, two weeks — and you read the list on the Friday.

Run it against one of my real lanes →

Bring one shipment you already argued about. We would rather run your file than show you ours.

Four sealed decisions from a bank's own supply chain → A buyer's own specification, at a border → The six scoped copies, as a static reference →
What you just proved. A redaction anybody can perform is a redaction anybody can forge — unless the record commits to the redactions before it is sealed. That is the whole mechanism, and you have now watched it refuse your own forgery of your own decision.
The engine in this page is 03-source/engine-bundle.js, built from the same lib-memory source as the server package and proven identical to it by parity.js (208 comparisons, 0 divergences). The criteria, the form, the gate, the receipt and the six projections are all produced by that engine; this page contributes styling and prose and no arithmetic.
No network request is made and nothing is stored in your browser.
Patent pending — U.S. Patent Application No. 19/747,068.

Everything on this site

Terms · Privacy · Licence · partners@corobate.com · Corobate LLC, North Carolina, USA