Standards, with the checks beside them.
What Milleleaf reads, writes and uses. Each claim stops at the check named here. No certification or blanket conformance is claimed.
What we use. What we have checked.
Used and tested means the named checks cover that use. It does not mean the product or every output has independent standards validation.
| Standard | Status | Use and limits | Test or check |
|---|---|---|---|
| OOXML: ECMA-376 / ISO/IEC 29500 | Used and tested | Reads and writes .docx, .xlsx and .pptx through WordCraft, GridCraft and DeckCraft. Writes Transitional. Full Strict support and independent OOXML conformance are not claimed. | hello-table run.sh, steps 6–14: Microsoft Office 16 fixtures, LibreOffice re-saves and edits. These checks cover the fixtures, not every OOXML feature. |
| ODF: OASIS ODF / ISO/IEC 26300 | Used and tested | Reads and writes ODT, ODS and ODP through LibreOffice conversion. No independently validated ODF version or profile is claimed. | hello-table run.sh, step 13: ODF export, LibreOffice edits and import. The format registry reports when LibreOffice is unavailable. |
| Canonical JSON: RFC 8785 | Used and tested | New layers and stacks use JCS canonical bytes for SHA-256 hashing. Numbers must fit I-JSON limits. | milleleaf-store: layers_are_stored_canonical_so_a_resaved_copy_keeps_its_name checks the RFC example and a pretty-printed copy. an_integer_beyond_2_53_is_refused checks the number limit. |
| Ed25519: RFC 8032 | Used and tested | Detached layer signatures. Signing leaves the layer hash unchanged. Trusted project keys and signature policy are checked separately. | milleleaf-store: signatures_are_detached_and_checked checks signing, verification and tampering; hybrid_signatures_old_keys_upgrade_and_policy checks the policy. |
| ML-DSA-65: FIPS 204 | Used and tested | A separate signature beside Ed25519. This is algorithm use, not FIPS module validation. The RustCrypto implementation is unaudited. | milleleaf-store: ml_dsa_65_matches_nist_acvp_and_wycheproof checks pinned NIST ACVP and Wycheproof subsets. |
| SLH-DSA: FIPS 205 | Used and tested | SLH-DSA-SHA2-192s adds a separate signature for owners, approvers and archive signing. No FIPS module validation is claimed. | milleleaf-store: slh_dsa_matches_nist_acvp and slh_dsa_fips205_and_rustcrypto_verify_each_other check vectors and two implementations. |
| HPKE: RFC 9180, with X-Wing | Used and tested | Sealing uses HPKE base mode, X-Wing, HKDF-SHA256 and AES-256-GCM. X-Wing is a draft hybrid KEM, not a final RFC-standard KEM. | milleleaf-seal: boringssl_seals_and_rustcrypto_opens_and_the_reverse and both_implementations_match_the_hpke_pq_test_vector. The published draft vector uses ChaCha20-Poly1305; AES-256-GCM is checked by interoperation, not a published vector. |
| Time-stamps: RFC 3161 | Used and tested | Stores TSA tokens over signature files. Rust checks the imprint and time only. It does not check the TSA signature or certificate chain. The user chooses the TSA. | milleleaf-store: a_time_stamp_token_is_checked_against_its_signature_file. hello-table run.sh step 15 checks a local test TSA with openssl ts -verify, including its signature and certificate. |
| OpenTimestamps | Used and tested | Writes .ots proofs and upgrades through chosen calendars. Pending proofs stay labelled pending. Offline verification does not claim Bitcoin confirmation; no qualified time-stamp claim. | hello-table run.sh step 15 uses a local test calendar for pending proofs. milleleaf-store: a_real_confirmed_proof_checks_offline checks a recorded proof against a recorded header. Online header checks alone do not prove best-chain membership. |
| DocLang 0.8 | Used and tested | Exports .dclg and .dclx for AI tools. It is an export, not a substitute for the signed source. | hello-table run.sh step 19 runs the hash-pinned doclang 0.8.0 validator on both exports and checks that it rejects a broken table. |
| WCAG 2.2 AA | Not claimed | This site targets WCAG 2.2 AA. Conformance is not claimed. | site/scripts/check.mjs checks keyboard skip-link focus, overflow, both colour themes and reduced motion. These checks are partial; a full accessibility assessment is still needed. |
| PDF/A-3b and PDF/UA | Planned | M3.5 plans independently validated archival and accessible PDF output. Current packs are plain PDF. Neither PDF/A nor PDF/UA is claimed. | Planned: veraPDF checks and a conformance statement. Slide pages need real text structure before an accessibility claim. |
| ISO 19650 workflow | Planned | M3 plans support for the ISO 19650 workflow: states, coded IDs, status, revision and two-step publication, alongside the existing CDE. | No workflow conformance claim. Planned support does not replace CDE security handling or assessed certification. |
Identity in the places the format allows.
Milleleaf uses content-control tags in Word, defined names in workbooks, shape names in decks and custom file properties. ECMA-376 defines these places. The files open normally in the checked apps.
The standard allows these markers. It does not promise an app will keep them, or that copying a table or slide will give it a new identity. Milleleaf checks survival per app, reports duplicate IDs and treats a content lock as a hint. A typed-over link is checked again on import.
Tests are named above so each claim has a boundary.