How we make claims. Checked before they publish.

A claim is a promise about evidence

So it is held to the same standard as the evidence. Every capability described on this site is tied to something demonstrable — a test, a release record, a verification on the live system — and we only describe capabilities that exist today.

Checked against what actually ships

Before this site can be published, its pages are checked automatically against that evidence. Everything described here reflects the current production system — the marketing cannot get ahead of the product, because the release stops if it does.

This line is permanent

Amberhold supports the people who carry a duty. It does not discharge it, certify it, or make a plant safe — no software does. A system that implied otherwise would invite a site to mistake a green screen for a competent person's judgement, which is the exact failure the evidence exists to guard against.

Why that makes the record worth more

A system that claims to judge compliance has an interest in the answer. Amberhold has none: it records what happened, including the parts nobody enjoys reading, and leaves the judgement to the people qualified to make it.

Said plainly, because procurement will ask

There is no certificate. What there is instead is evidence, all of it inspectable during procurement: UK-hosted infrastructure in the London region, least-privilege service accounts, encryption in transit and at rest, append-only evidence enforced by the database itself, audited administrative actions, daily backups with point-in-time recovery, and a rehearsed restore drill completed in fourteen minutes.

Offline is the working example

Amberhold opens without a signal and shows the plan as it was last synced, always stating its age — so nobody mistakes last week's round list for this morning's work. Recording a round while fully disconnected is in active development and is described that way, here and on the roadmap, rather than folded into the phrase ‘works offline’.

Integrations carry their own status inside the product

Each connection states what has been verified end to end against a live site and what is documented and ready to configure. A test prevents any of them being promoted without a dated evidence record behind it — the same gate this website runs under.