For the person you share with
You were sent a link to a PacSpace record. What it is, what to do with it, what the sentences mean, and how to keep a copy that does not depend on the link. No account needed.
Someone sent you a link to a record and, separately, a six-character code. This page is for you. You do not need an account, a key, or anything from PacSpace to use it.
What you were sent
A record is the sending organization's own account of something a system of theirs did: what it was, when, who or what acted, and the fingerprints of the files involved. They wrote it at the time. PacSpace committed it, and from then on neither they nor PacSpace can change it. The link opens that record, and your browser checks it against what was committed, in front of you, without asking PacSpace or the sender whether it is fine.
Written by one side. Visible to both. Owned by neither.
Open it
Open the link and enter the code where it asks. Nothing about the record is shown before the code. The check runs as the record opens; the first sentence is its result. "This record has 3 entries. All 3 are here, and all 3 match what was committed." is a pass. A sentence that names an entry, "Entry 2 does not match.", is a failure, and it is telling you that the copy your browser was served differs from what was committed.
Then read the record. Each day with entries opens to a table; each entry opens to what was written, its seal, and who wrote it and who acted. A day with no entries says so, and says what the entries on either side of it put it between.
What the check means, and what it does not
The check shows the record is unchanged since it was committed. It does not show that what was recorded was true. If the sender wrote something false, the record holds it faithfully, with the time and the actor. What you are getting is the certainty that this is what they wrote, when they wrote it, and that no one has changed it since, including them.
Satisfy yourself
Under the entries are "Change one character" and "Check again". Press the first, and your copy, in your browser, changes by one character; press the second, and the check catches it. "Restore" puts your copy back. Nothing you do on the page touches the record.
If you were given a file that the record is about, drop it where the page says "Drop the file here." Your browser fingerprints it and tells you whether it is in the record. The file is never uploaded.
Keep a copy
Two things outlive the link. "Print a statement" gives you a one-page statement with the record's name and reference, the count, every acknowledgment, when and where it was checked, and how to check again. "Download history" beside it gives you the record as a file. The fingerprint printed on the statement names that exact file. Keep both. With the file, anyone can run the same check later, with no link and no PacSpace:
npx @pacspace-io/check history.json --fingerprint 0x...Say that you checked
"Record that you checked this" is optional. It writes a record of its own, under the name the sender gave this link, that you checked these entries today and what the check found. The sender and anyone else they share the record with will see it. It is never required; the check works the same whether or not you press it.
If the link does not open
- "This link expired on 15 October." The record has not changed. Ask the sender for a new link.
- "Northwind Robotics has turned this link off." The sender ended it. The record has not changed, and they decide who holds a link to it.
- "This link does not open a record." Check the link you were sent, then ask the sender.
- "Too many tries. Wait 15 minutes." The code was wrong five times. Wait, then enter it again; the record has not changed.
- "PacSpace could not be reached from this browser, so this record has not been fetched and nothing was checked." Try again in a moment. If you already hold the history file, the checker above runs without PacSpace.
If the numbers do not agree with yours
The record is what the sender wrote. If it disagrees with your own records, the record is where the disagreement is now written down, with its times and its fingerprints, and both of you are reading the same one. Take it up with the sender; PacSpace holds no view on who is right and settles nothing.