← Wilder Robotics
Engagement receipt · Filed with IETF, 2026-07-30

Everyone is focused on building robots.
Somebody has to prove what they did.

Pask is the engagement receipt for the robot age — one signed record per engagement, held where the work happened, verifiable in any browser, offline and years later.

See it live at pask-witness.com

PASK-00045
Seal · VALID
Time
July 2, 2026 · 14:22 CDT
Asset
Patrol Robot 04
Outcome
Perimeter clear · 04:22 loop complete
Action
Patrol route A → return to dock
Result
Sealed. Committed to chain root.

Edit any blue field above.

Every receipt on this page was sealed with real keys on Pask's own reference site, a staged deployment we built and operate. The cryptography is real. The customer, so far, is us.

— William McKenzie and Rob Wilder, founders
01 · Custody

The key never leaves your building.

The signing key is generated inside a secure chip in the appliance you own. It cannot be exported, so no operator, no cloud, and not Pask ever holds a usable copy. Unplug the appliance and the key goes with you.

Keys
On-site secure chip
Format
Open · IETF RFC 9943 and 9942
Verifier
Offline, in any browser
02 · Lifecycle

One record, from charter to proof.

Every signed record follows the same five stages. Nothing is reconstructed after the fact.

01 · Chartered

The site signs its charter.

A plain-English founding document: what this site is, who may act on it, and what each device is allowed to do. Everything downstream is derived from it.

02 · Admitted

Each device joins under contract.

Every robot and sensor is admitted with a signed contract that states what it is and how it speaks. A device that cannot self-attest is represented by a gateway.

03 · Approved

A person approves the engagement.

Approval happens once, at the gate, against the charter, by a named party. Never per robot action in the loop. The robots then run exactly as they do today.

04 · Sealed

The appliance seals one record.

The on-site appliance witnesses the work and seals a single signed record: who did what, when, and under whose approval, committed to a hash on a key you hold.

05 · Proven

Anyone verifies it, offline.

The seal recomputes in any browser with no account and no call to us. Change one field of a sealed record and every signature stops verifying.

03 · Posture

Beside your robots. Never in the path.

Pask is a witness, not a vault: it watches, it never controls. Your robots keep speaking what they already speak, and you re-route nothing.

01
Each device joins with a signed contract that says what it is and what it may do.
02
The appliance reads each device on its own protocol, out of band and read-only. Approval happens once per engagement, never per robot action.
03
Each sealed record writes into the work-order or claim system you already run.
04 · For engineers

Filed with IETF on 2026-07-30 as draft-wilder-scitt-physical-site-engage-receipt-00, an individual submission profiling SCITT for tamper-evident receipts of physical-site engagements, building on IETF RFC 9943 and RFC 9942. The pask-workspace repository holds the current draft, reference implementation, and conformance vectors. This site runs on our own reference deployment.

When the dispute comes, you start from evidence, not reconstruction.