FolioRIRecords
As at
Sun 22 Nov 2026
Entries
10
Not yet
16
Page seal 4FEE, 087°24′. Drawn from the SHA 256 of this page’s source text4FEE
Page seal4FEE, 087°24′

How the record is sealed

How Marsadel seals each record, what the daily root is, which outside anchors are planned, and what a record does and does not prove.

Draft of 22 Nov 2026. Version 0.1.

Every unit we finish ends in a Proof of Fix record. This page says how that record is written down, how it is sealed, and how anyone can check that it has not been changed since.

Status today, 22 Nov 2026. The Register software runs on our own machine: it writes hash chained, signed entries, builds daily Merkle roots and has a verify command. It has not been used on client work. On 22 Nov 2026 it sealed our first four real records, read only assessments of domains the founder owns, one of them marsadel.com, with no change applied, checked by our rule based inspector only, and signed with a local key file that stands in for a key service; record MSD 0001 can be checked on the verify page. No root is anchored outside the firm, the production signing key below is not created, and the public per record verify lookup and the roots and keys pages are not live yet. This site has been live on marsadel.com since 22 Nov 2026, in English, and its verify page checks record MSD 0001. Target for the other public pages: the week of 30 Nov 2026. Until then, the outside parts of this page describe a design.1

1. The Register, in one paragraph

The Register is our log of everything that happens in a unit: the order, the authorisation, the proof of control, each change, each approval, each retest, the reviewer's signature, the record. Each entry is linked to the one before it by a hash. A hash is a short fingerprint of a piece of data: change one letter and the fingerprint changes. So changing an old entry would change every entry after it, and the change would show.

2. What goes into an entry

  • The kind of event, the time, and who acted: an agent, a person or the system.
  • A hash of the event's contents, not the contents themselves.
  • The hash of the previous entry.
  • A signature with our signing key, and the id of that key.

The contents sit in a separate store that we can delete. Every identifier is salted with a secret value for each client before it is hashed, so a hash cannot be matched against a public list of domains. A client's order files are deleted 12 months after the order, or at exit if that comes first; the salt is destroyed at the same time and the date is sealed.2 Details are on our privacy notice. Is your data used to train AI? No, unless you tick a consent box that allows it.

3. The daily root

Every day at 00:05 UTC a job builds one summary hash, a Merkle root, for each client's entries of the day, then one global root over all of them. A Merkle root lets anyone prove that one entry belongs to the day's set without seeing the other entries. Only the global root is published.3

The daily root is published in the C2SP checkpoint format, an open text format used by public logs.4

4. The signing key

  • One signing key, an Ed25519 key held in Amazon's key management service (AWS KMS). Every signed object names the key that signed it. AWS KMS supports Ed25519 signing (aws.amazon.com/about-aws/whats-new/2025/11/aws-kms-edwards-curve-digital-signature-algorithm, posted 7 Nov 2025, read 22 Nov 2026).5
  • The keys page will list every key with its purpose and the dates it is valid. When a key is replaced, the change will itself be an entry in the Register.6
  • Public keys are also published as /.well-known/jwks.json and keys.json.7

5. Outside anchoring

A log we keep ourselves could, in principle, be rewritten by us. Anchors put a copy of each day's root in places we do not control, with a time, so a rewrite would not match them.

AnchorWhat it doesStatus
OpenTimestampsPuts the day's root into a public timestamp that anyone can check later. Free to useNot yet: first daily root anchored, planned from the week of 23 Nov 20268
Public GitHub commitWrites the day's root into a public repository with a dated commitNot yet: repository named and first commit made, planned from the week of 23 Nov 20269
RFC 3161 timestampA signed timestamp from a timestamp authority, under the RFC 3161 standardNot yet: authority chosen; planned after Mon 14 Dec 202610
Locked storage copyEach root stored in Amazon S3 with Object Lock in compliance mode, in a separate account, so no user can overwrite or delete it during the lock periodNot yet: account and bucket set up, planned after Mon 14 Dec 2026; the AWS page on compliance mode reopened and quoted11
WitnessesOthers sign the day's root too: our own second cloud account first, then a partner, then a public witness network if one acceptsNot yet: own second cloud witness, planned after Mon 14 Dec 2026; partner and public witnesses only once one agrees in writing12

Each record's verify page shows which anchors hold its day's root and how many witnesses signed it.

6. How to check a record

The verify page for a record has a Verify button. It recomputes the record's path to the published daily root in your own browser, and checks that root against its anchors. You do not need to trust our server's answer; your browser does the sums.13

From Feb 2027 we plan to publish an offline verifier and the record format, with test vectors, so anyone can check records without our site.14

7. Forecasts sealed before the outcome

Before each run on our own domains, we seal what we expect: that Stage A passes in 72 hours, the dates of quarantine and reject, the human minutes. Afterwards we seal what happened. Our rule, published on the first day: a rate enters a published figure only if its forecast was sealed first; anything assembled later prints apart, marked backfill. A forecast sealed with a date cannot be changed later without the change showing.15

8. What a record proves, and what it does not

It proves that the record existed in this form by the time of its anchors, and that it has not been changed since without the change showing. It proves which tests were run, what they returned, which steps agents did, which model checked them, and which human signed.

It does not prove that the work was right in every respect. That rests on the acceptance tests, the second model, the human reviewer and the rechecks at 30, 90 and 365 days, each printed on the record. It does not prove that your domain is still in the same state today; a fresh check does that.

9. If something breaks

If a daily root is missed, the gap is printed on the roots page with its date and cause. We do not fill a gap after the fact. If a key is exposed, we replace it, publish the replacement as a Register entry and mark every object signed after the exposure for review.

10. Contact for problems with the record

Report a problem with a record, a root or a key in writing to contact listed in /.well-known/security.txt once mail records and a mailbox are set up on marsadel.com16. A record is named like MSD 0001; quote that name.


Source: Marsadel master plan v2, sections 3.2 item 4, 3.4, 8.2 and 8.4. OpenTimestamps is free to use (opentimestamps.org, read 22 Nov 2026, plan source S68). AWS KMS Ed25519 support (plan source S147) was read on AWS's own page on 22 Nov 2026 (posted 7 Nov 2025). S3 Object Lock compliance mode (plan source S67) is not yet read on AWS's own pages and stays marked Not yet above.

Not yet in place16
  1. 1first daily root anchored outside the firm; per record verify lookup, /roots and /keys pages live on marsadel.com
  2. 2retention rule checked against the 365 day recheck, which falls after 12 months; rule confirmed before the first paid order
  3. 3first root published
  4. 4checkpoint format live, plan week 2
  5. 5key created
  6. 6signing key created and listed on /keys
  7. 7files live, plan week 2
  8. 8first daily root anchored, planned from the week of 23 Nov 2026
  9. 9repository named and first commit made, planned from the week of 23 Nov 2026
  10. 10authority chosen; planned after Mon 14 Dec 2026
  11. 11account and bucket set up, planned after Mon 14 Dec 2026; the AWS page on compliance mode reopened and quoted
  12. 12own second cloud witness, planned after Mon 14 Dec 2026; partner and public witnesses only once one agrees in writing
  13. 13Verify button built, plan week 2
  14. 14offline verifier published
  15. 15rule published as a GitHub commit on Mon 23 Nov 2026
  16. 16contact listed in /.well-known/security.txt once mail records and a mailbox are set up on marsadel.com

Each item is also marked where it stands on this page.