Skip to content

The statement and the check without PacSpace

A Shared Record can print a one-page statement, and a reader who keeps the history file can run the same check later with no link, no account, and no PacSpace.

Two things outlive the link. The printed statement is a page a reader can file, hand to a third person, or attach to a report. The history file is the record itself, in a form the standalone checker can check on any machine. Together they mean the record stands on its own when the link has expired and when PacSpace cannot be reached.

The Shared Record offers "Print a statement" once a daily statement covers every entry of the record. A daily statement is PacSpace's own line for each day, and a record is spoken for as of one of those days, so an entry committed today becomes printable after the next daily statement; until then the page says when. The control opens the statement page, which fetches the history through the same link, runs the check in the reader's browser, and prints only when the browser's result and what PacSpace holds agree. If they disagree, nothing prints and the page says so.

Page one, in order:

  • The heading, the record's name, and its reference, so two records with the same name are never mistaken for one.
  • Whose record it is and whose word each fact is: "This is a record kept by Northwind Robotics of one model build. What each entry says, and when it says the thing happened, is what Northwind Robotics wrote. When each entry was committed, and that none has changed since, is what the check confirms."
  • The count as of the daily statement: how many entries the record has, that all of them match what was committed, and that nothing was added between that statement and this check.
  • Every acknowledgment on the record, one line each.
  • The boundary: "The check shows the record is unchanged since it was committed. It does not show that what was recorded was true."
  • When and where it was checked, and whose clock: "Checked in a browser on 20 September 2026, 09:12 UTC, from the link below. The committed times above are part of the record; the time of this check is the time on the computer that ran it."
  • The link it was printed from, and the date the link stops working.
  • How to check again, with the link and without it.
  • The fingerprint of the history file, and why to keep the file.

Page two lists the entries: number, title, when it happened, when it was committed, each fingerprint and its size, and any amendment lines ("Entry 4 amends entry 2"; "Amended by entry 4 on 14 September").

Download history

Beside Print, "Download history" saves the history file the browser checked. The fingerprint printed on the statement names that exact file, so a reader can show later that the file they kept is the one the statement was printed over. The paper says it in one line: "Keep that file. With it and that fingerprint, the check can be run without this link."

The check without PacSpace

With the file and the fingerprint, anyone runs the same check on their own machine:

bash
npx @pacspace-io/check history.json --fingerprint 0x7079b0ac...

The checker recomputes the file's fingerprint, checks every entry against what was committed, names any entry the file does not carry, reads the record's current state from the public source, compares the daily statement, and says whether the fingerprint you gave names this file. It never calls PacSpace, and it does not need the link. See Check for its options and exit codes.

The paper's own words for it: "To check again, open the link in any browser and enter the code you were given with it. The check runs on its own when the record opens. It asks nothing of PacSpace or of Northwind Robotics while it runs. If this link has expired, ask Northwind Robotics for a new one, or run the check yourself: with the history file and the fingerprint below, npx @pacspace-io/check history.json runs it without this link and without PacSpace."

What a statement is not

It is not a certificate from PacSpace and it carries no judgment. It prints what the record says, what the check found, and who acknowledged it, in the order they were committed, and adds no adjective. When two acknowledgments of the same record disagree, both lines print, each with its own finding, and the reader is left with the record.