Future contributors
Clio is not accepting public submissions yet, and there is no account to sign into. What you can do on this page is real: generate an ML-DSA-65 owner key in this browser, see its did:maatara identifier, and set up how you will unlock it again.
Local identity
The private key never leaves this browser. It is generated in memory, shown to you once as a recovery phrase, and then wrapped — encrypted with a passkey or a passphrase you choose — before anything touches this device's storage. Clio never sees the plain key, because Clio is not part of this step at all.
This calls the browser custody module's real key generator: ML-DSA-65 (FIPS 204) key generation, then the canonical did:maatara derivation used everywhere else in Clio's trust source. The cryptographic engine (WebAssembly, roughly a megabyte) loads only when you press this button, not before.
If you lose this phrase and lose every device where this identity has been unlocked, nobody can recover it — not you, and not Clio. There is no password reset for a key that only you hold. Already-published record versions and receipts made under this identity would stay valid forever; you would just be unable to sign new ones. Write the phrase down or store it somewhere durable, separate from this device.
The kit file alone restores nothing — it is encrypted and useless without the phrase above. The phrase alone also restores nothing without either the kit file or a device that already has this identity unlocked. Keep the two of them apart from each other.
Type the three requested words back, exactly as shown above.
This device already has a wrapped copy of stored from an earlier visit.
Not your identity, or starting fresh on this device?
Uses this device's own authenticator — fingerprint, face, PIN or security key — through WebAuthn's PRF extension. Not every browser or authenticator supports this yet.
Sign a short message locally and verify it locally, entirely in this tab. This does not create a record and sends nothing anywhere.
If you already generated an identity — here or on another device — and saved its recovery phrase and kit file, you can bring it back on this device. This still never contacts a server; both the file and the phrase are read only in this tab.
Planned workflow
The steps are deliberately separate: publishing, review and DOI registration each have their own status. A record can be public and unreviewed; a DOI can be pending; neither condition is a quality verdict.
You can already generate that owner-controlled did:maatara in this browser, above. Linking it to a Clio account still needs an account service and an owner-signed link ceremony that do not exist yet. When they do, the account login will authenticate access only — it will never be the source of the identity itself.
Prepare event, authorship, rights and record-type information alongside the original media or supporting material. Standards fields and sensitive information will be handled according to the record type and access policy.
You will need permission to deposit the material and a suitable licence. Exact locations, human privacy, Indigenous knowledge, sensitive species and culturally governed material may require restriction, generalisation or refusal from an open collection.
After required metadata, object checks, signature and safety checks pass, a valid record is intended to receive a stable Clio URI. Later corrections will be new linked versions, never silent replacements.
Clio plans to record publication, discoverability, editorial review and DOI progress separately. A Clio trust log with Ma’atara integration in progress will pair your personal Veritas chain with a separate Clio institutional receipt.
Readiness checklist
Plain-language promises
No curator has made a finding under Clio’s published standard. It does not mean the record is low quality.
Once DOI operations are live, every accepted item will enter one registration job. Clio will not display an identifier as registered until a provider confirms it.
Corrections remain linked to prior versions. A hidden record can retain a resolvable landing page while being excluded from discovery.