Does the file follow UD 0.1.0?
Universal Document 0.1.0 · open implementation
Build software that speaks Universal Document.
Everything required to emit and test canonical UDR, UDS and BrowserCarrier files—without private knowledge, a hosted API, or a proprietary application package.
Start here
One format. Four separate answers.
Compatibility, integrity, mathematical signature validity, and real-world identity trust are never collapsed into one green badge.
Does the protected UDS content match its seal hash?
Is the signature mathematically valid for the supplied key?
Is that key trusted for a verified real-world signer?
Implementation kit
Nothing important is hidden inside our apps.
Normative implementation profileMinimum rules for interoperable UDR, UDS and BrowserCarrier output.Download →Canonical JSON SchemaThe existing 0.1.0 machine-readable schema, published unchanged.Download →Compatibility profileVersions, enums, policies, algorithms and verification boundaries.Download →Validation codesStable structured result vocabulary.Download →Golden-vector manifestKnown-good and known-bad artifacts with hashes and expected results.Download →Compatibility runnerLocal Node.js CLI for raw UD and BrowserCarriers.Download →
Lifecycle
Create → revise → finalize → verify
- Create UDR. Emit the required envelope, ordered blocks, metadata and manifest.
- Append revision. Preserve prior records and link the next record to its parent hash.
- Finalize UDS. Calculate the existing canonical hash and add the existing seal representation.
- Verify honestly. Report format, integrity, signature and identity separately.
- Carry in HTML. Embed the exact canonical bytes in an inert, offline BrowserCarrier.
Guides
Small enough to reproduce.
Hello World implementationLanguage-neutral algorithmsControlled Python referenceOptional API pathPublic samplesLocal developer sandboxNO UPLOAD
Do not upload confidential, regulated, or sensitive production documents solely for compatibility testing. This quick check runs locally in this browser.
Compatibility corpus
Eleven required scenarios, twelve inspectable files.
V1 and V2 are separate files for the revision scenario. The corpus also covers a broken parent chain, tampering, wrong-key/not-trusted boundaries, carriers, and malformed input.
node compatibility-runner.mjs vectors/06-valid.uds