# Your floor records that a button was pressed

> worklists.app — 2026-08-20
> Written for VC-7 — the 3PL and cold-chain custody org — the 3PL ops director who lost a chargeback dispute last quarter with a complete task log in hand.

One thesis: **your floor records that a button was pressed, and the people who ask you to prove
work happened — an auditor, a customer, a chargeback panel — do not accept that, because a tap is a
claim your system makes about itself.** The fix is not a better report over the same tap. It is a
task that closes with evidence.

## What the log actually says

Pull the task log for last Tuesday's inbound at dock 12. It says a receiving task for forty cases
of lettuce was completed at 06:14 by the login on scanner 7. It looks like a record. Read it the
way a chargeback panel reads it:

- *Completed* means a session tapped Done. The system did not see a pallet.
- *By the login on scanner 7* means whoever had scanner 7. Shared devices, shared logins,
  temporary labor on the dock — the log does not know.
- *At 06:14* is when the tap was received. Not when the count was done, if it was done.

None of that is your WMS lying. It is being exactly as honest as a boolean can be. When the
customer says thirty-eight cases arrived and you say forty, you produce this log, and the panel
reads a tap.

## What the panel accepts

A record that can be checked by someone who does not trust your application. Three things, and
all three have to be present:

**A real *who*.** Not a device login — an attested identity, bound to the person holding the
device at the moment of the act, through a path that did not pass through your app's code.

**A real place.** A read point the scan happened at, attested the same way.

**Inside the window.** A timestamp on the event itself, from the capture, compared against the
window the task was dispatched with.

That is what *attested capture* means, and it is what closes a task on this app. The close is not a
tap. The close is a scan of the pallet's mark, attested and landed on the event spine, and the task
closes with the hash of that event. **The record of work done is the same object as the evidence
it happened.** There is nothing to cross-reference because there are not two things.

## What changes on the dock, and what does not

Your receivers already scan. They scan the SSCC on the pallet today, and the scan goes into the
WMS. What changes is what happens next: instead of the scan populating a field and a tap closing a
task, the scan *is* the close. One motion. The receiver points the camera at the mark, and if the
worklist held exactly one task that mark satisfies, that task is done. No confirm dialog, no form,
no reading on the critical path — which matters when the hand is gloved and the dock is at 28°F.

If the scan matches two tasks, the app stops and shows both rather than guessing. If it matches
none, the event still lands and stands on its own. **A scan that closed no task is not an error.**
Your receiver's record of what they did does not depend on a dispatcher having predicted it.

## The dispute, replayed

Same Tuesday, same forty cases. The customer says thirty-eight. You pull the task, and it shows:
dispatched from their PO; closed at 06:14 with an event hash; the event shows the attested receiver,
dock 12, the pallet's SSCC, and a count of forty, with the attestation grade on it.

Now the argument is about whether the count was right, which is a real argument you can have. It
is no longer about whether the count happened, which is the argument you lose with a tap.

And if the count was wrong — if a recount finds thirty-eight — the correction is itself an event on
the spine, naming the one it corrects. Nothing is overwritten. The panel sees a record that admits
its own mistakes in order, which is the kind of record panels believe.

## What you are buying

Not a better WMS. The WMS keeps doing what it does. You are putting an app on the floor, under your
own name, whose only job on the critical path is to produce that hash — and whose design refuses
to produce anything cheaper. `complete` on the work door behind it, [worklists.dev](https://worklists.dev),
takes an event hash, not a boolean, and refuses `true` with a typed error.

Your task log will keep saying a button was pressed until a different thing is pressed. Get started
with an evaluation deployment on your own devices, run one inbound through it, and read the record
it leaves. Then read Tuesday's.

---
Get started: https://worklists.app/get-access/ · All posts: https://worklists.app/blog/ · Machine face: https://worklists.app/llms.txt · Product document: https://worklists.app/product.md