This month's content walked through a lot of individual pieces, one audience or one mechanic at a time. It's worth pulling all of it together into a single, plain list of what's actually available today, without the segment-specific framing.
Sealing
Any file, any format, can be hashed and bound to a qualified electronic timestamp issued by Swisscom Trust Services, accredited under both ZertES and eIDAS. The hash is a fingerprint of the exact bytes, so any later change to the file is detectable. The timestamp carries a legal presumption of accuracy under eIDAS Article 41, for both the date it shows and the integrity of the data it's bound to. Files can be sealed individually or as a batch across a whole content library.
Declaring
Alongside a seal, a declaration records how the work was made: human authored, AI-assisted, or AI-generated. This is a contemporaneous statement, made at the moment the content is finalized, which is what gives it more weight than a label added or reconstructed later. It's also the kind of record that EU AI Act Article 50's transparency obligation is asking for.
Signing
A qualified electronic signature carries the same legal standing as a handwritten signature under OR Article 14 paragraph 2bis in Switzerland, and meets eIDAS requirements in the EU. When a document needs more than one signature, each signer's identity and signature are independently verifiable, not bundled into a single completion status.
Checking
Two separate tools cover two separate situations. /verify checks a sealed record by certificate ID, hash, uploaded file, or pasted text, confirming whether it matches what was originally sealed. /validate checks any signed PDF you receive from someone else, returning a verdict on its qualified timestamp, signer identity, and eIDAS/ZertES compliance, with no account required either way.
Why this is one toolkit, not four separate ones
Sealing, declaring, signing, and checking answer different questions, but they're built on the same underlying mechanics: a hash of exact content, a qualified timestamp with legal standing, and a verified identity where one is needed. Whichever piece of this a specific situation calls for, it's drawing from the same verifiable foundation as the rest.
