Recordation
What it means to record an action so that the record stands on its own afterward, and what PacSpace does and does not claim about it.
The problem with your own logs
When a system acts, it writes down what it did. That account lives inside the system that wrote it, under the same keys, within reach of the same people and the same software. When something goes wrong, the record of what happened is the thing everyone needs and the thing least able to speak for itself. It was written by one side, it can be rewritten by that side, and nobody outside can tell.
Recordation is the practice of writing the record somewhere else as the work happens, so that afterward there is a record, not an argument.
What a recorded entry is
An entry is your own description of one action: a title a person can read, when it happened, who or what did it, and the fingerprints of the files it names. You write it at the time. PacSpace commits it, and from then on the entry cannot be changed by you, by PacSpace, or by anyone else. Every later entry in the record is committed after the ones before it, so the order is part of the record.
The side that did the work writes the entry, in its own words. Anyone that side hands the link to can read it and check it. Neither side can change it afterward, and PacSpace cannot either. Shared. Fixed. Private.
What the check shows
When someone opens a Shared Record, their browser checks every committed entry against what was committed. When someone holds only the history file, the standalone checker does the same without PacSpace. A passing check means: these entries are exactly what was committed, in this order, and nothing has been changed since. A failing check names the entry that no longer matches.
The check shows the record is unchanged since it was committed. It does not show that what was recorded was true. If a system wrote a false entry, the record faithfully holds a false entry, and it holds the time and the actor that wrote it.
What PacSpace does not do
PacSpace records and never decides. It does not watch your systems, judge their actions, or stop them. It does not detect a break-in or prevent one. It never holds your files: it receives a fingerprint and a size, and the file stays where it was. It shows an entry only to the people you share it with.
What it gives you is this: afterward, when an evaluator, an auditor, a program office, a customer, or another company's system asks what happened, there is a record that was written at the time, that neither side can edit, and that they can check themselves. Flying works this way: every flight carries a recorder no one on the plane can alter, and investigators read it afterward. PacSpace is the flight recorder for AI agents.
Custody
PacSpace keeps the record. You keep the files. A record proves that a fingerprint was committed, and when, and that the description sealed with it has not changed. It does not prove the file exists today or where it is. Keep the objects and keep your copies of the receipts, and the record will stand on its own with PacSpace unreachable.