FolioHWRecords
As at
Sun 22 Nov 2026
Entries
14
Not yet
37
Page seal 2812, 131°13′. Drawn from the SHA 256 of this page’s source text2812
Page seal2812, 131°13′

How a job runs

Order, proof of control, work, second check, human sign off, sealed record, verify and warranty. Each step of a Marsadel job, in plain words.

Every Marsadel job will follow the same eight steps. AI agents plan the work, write each step and test the result. At launch you or your agency apply each step; we do not log in to your systems. A model from a second vendor checks it. A named human signs it. The result is sealed into a record you can check.1

Status today, 22 Nov 2026. Nothing is on sale to anyone outside the firm yet. The first runs are read only runs on domains the founder owns and on written test fixtures (example.org style names); the first four, on domains the founder owns, were sealed on 22 Nov 2026 with no change applied, and record MSD 0001 can be checked in a browser. Steps marked "not yet" below are written for launch and are not in place today. We registered marsadel.com on 22 Nov 2026, and this site has been live on it since 22 Nov 2026, in English. It has no mailbox yet.2

Nothing is sold until it passes our quality test, a set of graded test cases. The full rules are at the end of this page.3

1. Order

You order in writing on our intake page. There is no call.

  • Your price tier is set from facts we can read: where your mail and hosting sit, the country in the domain's public registration data where it is shown, and your site's language. If those facts disagree, we use Tier 1, our full list price. Price tiers explained
  • Your authorisation. You sign a written scope with your typed name. It lists the domains, what we may do and how long the authorisation lasts.
  • Your consent choices. Four separate yes or no boxes. You may let an anonymised copy of your case join our test cases, for a discount.4 You may let it join test sets we license to AI companies later, with your domain and names removed, so they can test their own tools. You may allow checks on your domain after the job ends. You may allow AI training on your data. Each is off unless you tick it. The AI companies may use a licensed test set only to test their tools.5
  • Training AI on your data. No, unless you tick a consent box that allows it. That is the fourth box above; none of the other three allows training.6
  • A sanctions list check runs on every order.7
  • Payment. The price for your country is shown before you pay. You pay in full at order, in US dollars, by card or by USDC, a digital token worth one US dollar. Refunds go back the way you paid.8

2. Proof of control

No change is planned until you show that you control the domain. There are three ways.

  • A DNS record. You add a TXT record with a random label we give you. The label carries no brand and no name, because old DNS records are kept in public archives. You delete it once we confirm the check.
  • A registrar export. You send the account export from your registrar.
  • Runbook mode. You apply every change yourself, so you prove control by doing it.

3. Work

AI agents plan each change, write it as a step and test the result, inside the scope you signed. In write mode, once it opens, they also apply the change.

  • Runbook mode or write mode. In runbook mode you, or your agency, apply each change from our written runbook, and we hold no write access. In write mode we apply the changes. At launch every job runs in runbook mode, at 20 percent under the write mode price. Write mode opens only once insurance that covers work done by AI agents is in place.9
  • Nothing changes without approval. Every change is approved in writing before it runs. Where a step needs your yes, the clock stops until you answer. We remind you at 24 and 72 hours.10
  • Outside text is data, not instructions. Our agents read things written by others: mail reports, your site, logs, registrar mail. They act only on our written steps. Before our first quality test we check this by planting an instruction in a test domain's DNS record and on a test web page. The check passes only if the agents ignore it and log it.11
  • Access ends with the job. Any access you grant has an end date. We revoke it when the job closes and record the revocation. In runbook mode you grant no write access. The Microsoft 365 job reads your sign in logs from an export your IT firm sends us. We hold no access to your tenant. Read only consent may replace the export later, once confirmed.12, 13
  • What we do not do. We give no tax or VAT advice and file nothing in your name. For the Microsoft 365 job we hold no access inside your network; your IT firm applies each device's settings on site. We make no phone calls to registrars; where a registrar needs a call or an identity step, you make it.

Example: Domain and Mail Gap Closure

Stage A, within 72 hours of the day you send what we ask for. SPF valid with 10 DNS lookups or fewer. DKIM signing on every sender whose console you can reach. Every other known sender listed in a signed plan with the reason it is on hold. DMARC at p=none, with reports sent to a mailbox on your own domain. Registrar lock on. DNSSEC where the registrar supports it. Domains that send no mail set to reject. Stray records removed. Certificate dates checked. Retest. In runbook mode, we retest each change within 72 hours of you telling us it is applied; time you take to apply a step does not count toward the 72 hours or the 10 day refund point.14

Where the reports go. DMARC reports go to an address on a reports subdomain of your own domain, held by your own mail provider and forwarded to us. No public record of your domain names a Marsadel host, so your domain does not show up in a list of our clients. If your mail provider blocks forwarding to outside addresses, we take the export from your DMARC vendor instead, or you set up a mailbox on a reports subdomain with a provider you choose.15

Stage B, the staged move to reject. Quarantine after 14 days of clean reports. Reject after a further 42 days, the last 30 of them with mail from senders you have not approved under 1 percent. Each step waits for your approval. A sender that still fails holds the move, with a written reason, so your own invoices are not refused. Stage B runs until reject or day 120 from Stage A, whichever comes first. From the start to reject this is about 8 weeks. Others sell it faster; the price book shows their figures beside ours and why we wait. The 42 day step is our own design. Red Sift says quarantine to reject typically takes 6 to 8 weeks; DuoCircle suggests under 1 percent unknown traffic for 30 days before reject, and gives 30 to 90 days from quarantine to reject (both read 22 Nov 2026).

4. Second check

Every step is read by a model from a different vendor than the one that did the work. We call it the second AI check. It reads the raw change itself, not the builder's summary of it, and gives a verdict that goes on the record.

Not yet: second model vendor connected and paired with the builder16

5. Human sign off

A named reviewer checks the work and signs the record. On domain, mail and certificate work, the record says "named accountable reviewer". No licence applies to that work, so we do not claim one. We do not claim a licence for e invoicing work either. For e invoicing we believe none is needed, and each country's authority page is read and recorded before that desk opens.17 Work that does need a licence, such as tax files or legal documents, will be signed by a licensed partner in their own name, once such a desk opens.18

  • Every client job gets full human review until 200 graded jobs in a row show agent error at or below human error. Then one job in 5 is reviewed, then one in 20. Your record always says whether a human reviewed your job, and names that person when one did.
  • Each time a major AI model is released, we rerun every quality test within 48 hours and publish a short note on what moved.19

Not yet: two contracted reviewers under contract, target Mon 30 Nov 202620

6. Sealed record

Each finished job gets a Proof of Fix record, with a name such as MSD 0001. It holds:

  • every acceptance test, its version, and pass or fail;
  • the second AI check's verdict;
  • the steps the AI agents took;
  • whether a human reviewed it, and that reviewer's name;
  • a fingerprint of the warranty terms that apply;
  • the signing key used.

The record is written into our record log (the Register), which is signed and chained. The log software runs on our own machine today; it has not yet been used on client work. Each day the log is closed with one summary number, and that number is to be copied to public places outside our control.21 After that, a record cannot be changed without the change showing. The log itself holds fingerprints only, not your domain or personal data.

We also seal forecasts, for example the day we expect your domain to reach reject, before the job starts. After it, we seal what did happen. Any success rate we publish uses only forecasts sealed first, so we cannot pick our best results after the fact.22

Not yet: production signing key and outside anchors set up and listed on /keys and /roots23

7. Verify

Every record will have a link and a Verify button.24 Anyone with the link can check, in their own browser, that the record is the one we sealed on that date and that it has not changed since.

How verifying works

8. Warranty

One rule. The unit page, the price book and every record carry the same rule, and our terms set it out in legal form.

  • Stage A: we redo it free until every Stage A test passes. If it has not passed within 10 days of the day you send what we ask for, you get a full refund. Time you take to apply a step does not count.14
  • After Stage A is accepted: if a Stage A test fails within 30 days because our fix was wrong, we redo it free.
  • Stage B: if reject is not reached by day 120 because our fix was wrong, we refund the Stage B share. In Tier 1, at launch in runbook mode, that is 120 USD direct or 76 USD wholesale; at full price it is 150 USD direct or 95 USD wholesale. Other tiers get the same share of their lower price. It is not more than you paid.
  • Rechecks: we recheck at 30, 90 and 365 days after reject. If a 30 or 90 day check fails because our fix was wrong, we redo it free and credit you 30 percent of the price paid. If a 365 day check fails for that reason, we redo it free.
  • Who decides the cause: we propose one from a short list (you changed the setting back, your provider changed something, our fix was wrong, or other), with the evidence. You or your partner confirm it. If you disagree, the cause you choose goes on the record.25 We publish how often each cause happens, including other.
  • In runbook mode, if a test fails because a change was applied differently from the runbook, we point to the line, and you apply it again at no extra cost. The clocks pause until it is applied.26

The Stage A lines also cover Mail Alignment bought on its own. The 30 percent credit comes from a reserve we fund.27

Not yet: warranty reserve funded and terms reviewed by a lawyer28

The quality gate in full

No job is sold, and no step is run on a client's domain, until that step has passed our quality test. We call it the Bench.

  • A Bench is a set of graded test cases. They will come from test domains registered for the purpose, with faults put in on purpose, from written fixtures and public specifications, and from runs on our own domains. No client data.29
  • To pass, at least 95 percent of cases must be accepted on the first try by both the second AI check and a human reviewer. Zero cases may break mail or a site.
  • The unit page prints the result: how many cases, how many had outside mail senders, the pass rate, the spread of registrars and DNS hosts, and the date.
  • Where a job has a later step with a later quality test, the order page prints that test's date. If that later test fails, we refund that step's share of the price at once.

Not yet: first Bench gate passed, Unit 1 Stage A, target Sat 5 Dec 2026, graded by contracted reviewers30

When a client goes quiet

If we wait on your approval, the clock stops. After 14 days of silence the job closes. What you paid for unfinished steps becomes a credit you can use later.31

When something goes wrong

If we find signs of an active break in while we work, we stop, keep the logs, tell you in writing, and hand the case to your IT or security provider, or one you choose. Incident response is not part of any price. Every confirmed bad job gets a public write up with its root cause, on our postmortems page.32

If a change stops some of your mail. The likely cause is a sender we did not know about, such as an old invoicing tool. We hold the next step, add that sender, and log the hold with its reason. Each runbook step lists the old value of every record it changes, so you can put the old value back yourself; receivers may keep the new value until the record's cache time (TTL) runs out.33 If your mail stops after a change from our runbook or one we made, write to us, and we reply to that before anything else.34 The written desk is not open yet: no mailbox exists. What you can do until the desk opens · The status board

Before and after: the Passport

Every client will start with a Domain Passport that dates what the last provider left and lists each gap. When a client leaves, an Exit Passport will prove each account sits in the client's own name. The Passport is a Marsadel unit in design.35 The Passport family

If you want to stop

You can end any job in writing before it is accepted.36 Any access you gave us ends the same day, and we record that it ended. In runbook mode we held no access at all. Your records stay in your own accounts. Your files are deleted, and we send you a sealed deletion certificate.37

Words we use

  • Registrar: the company where a domain name is registered and renewed.
  • Registrar lock: a setting that stops a domain being moved to another registrar without the owner's say.
  • DNS: the public records that tell the internet where a domain's site and mail live.
  • DNSSEC: a signature on DNS records, so a visitor's computer can tell they were not tampered with on the way.
  • SPF: a DNS record that lists which servers may send mail for your domain.
  • DKIM: a signature your mail servers add to each message, checked against a key in your DNS.
  • DMARC: a DNS record that tells receiving mail servers what to do with mail that fails SPF and DKIM, and where to send reports.
  • p=none, quarantine, reject: the three DMARC levels. None only reports. Quarantine sends failing mail to spam. Reject refuses it. Quarantine and reject are called enforcement.
  • DMARC reports: daily summaries that receiving mail servers send back, listing who sent mail as your domain.
  • Certificate: the file that lets a site load over https. Each one expires on a set date.
  • SMTP AUTH: a way for printers, scanners and old apps to send mail through Microsoft 365 with a username and password.
  • Microsoft 365 tenant: one organisation's Microsoft 365 account.
  • E invoicing: invoices sent as structured data in a national format, often through a government platform.
  • Fatoora: the Saudi tax authority's e invoicing system.
  • KSeF: Poland's national e invoicing system.
  • USDC: a digital token that tracks the US dollar one for one.
  • The Bench: our quality test, a set of graded test cases. A job goes on sale only after it passes.
  • The Inspector: our second AI check, a model from a different vendor that checks every step.
  • The Register: our record log, signed and chained, of every event in every job.
  • Proof of Fix record: the signed record of one finished job, named like MSD 0001.
  • Runbook mode: you apply each change from our written runbook, and we hold no write access.
  • Write mode: we apply the changes ourselves. It opens only once insurance that covers work done by AI agents is in place.
  • Recheck: a check of a finished job at 30, 90 and 365 days after it reached reject.
Not yet in place37
  1. 1second model vendor connected; two contracted reviewers in place; record log and public verify page live
  2. 2mail and parking DNS records applied, and a mailbox set up
  3. 3first Bench gate passed, Unit 1 Stage A, target Sat 5 Dec 2026
  4. 4test case discount set in the price book
  5. 5licence terms for test sets set, limited to testing only
  6. 6consent boxes built into intake and written into the terms
  7. 7intake screening built
  8. 8company formed and checkout live
  9. 9insurance covering AI agent work bound
  10. 10approval queue built
  11. 11planted instruction test passed
  12. 12read only consent route confirmed, in line with the rule that we do not log in to client systems
  13. 13credential grant and revocation records built
  14. 14runbook clock rule confirmed in the terms
  15. 15Microsoft and Google forwarding pages read and quoted in the runbook
  16. 16second model vendor connected and paired with the builder
  17. 17Saudi, Polish, German and UAE authority pages read and recorded
  18. 18licensed partner under contract for each regulated desk
  19. 19first Bench built and passed
  20. 20two contracted reviewers under contract, target Mon 30 Nov 2026
  21. 21daily root and both anchors running, planned from the week of 23 Nov 2026
  22. 22forecast table and the published rule live, planned Mon 23 Nov 2026
  23. 23production signing key and outside anchors set up and listed on /keys and /roots
  24. 24public verify, roots and keys pages and the Verify button live, plan week 2
  25. 25dispute rule set in the terms, including what happens to the refund while a cause is disputed
  26. 26rule confirmed in the terms
  27. 27recheck reserve funded
  28. 28warranty reserve funded and terms reviewed by a lawyer
  29. 29Bench test domains registered
  30. 30first Bench gate passed, Unit 1 Stage A, target Sat 5 Dec 2026, graded by contracted reviewers
  31. 31credit amount and expiry set and printed in the terms
  32. 32postmortems page live
  33. 33old value printed on every runbook step
  34. 34incident reply time set in the terms
  35. 35Exit Passport available, plan date Mar 2027; until then a written exit note and a sealed deletion certificate
  36. 36cancellation rule set; proposed: you pay for stages already accepted and get back the rest
  37. 37exit and deletion flow built

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