LibreOffice (ODF)

1. Overview

Full desktop office suite running 100% offline. Native files are standard zip containers holding documented XML (`content.xml`) extractable with basic POSIX unzip.

Category: Knowledge & Office.

2. Version and scope assessed

Version assessed: Source commit 568bac1a5c057f8ec1f43f6d3dae1a9ad0509708.

4. Principle profile

5. Fundamental requirements

6. Evidence and verification

• E1: The published resolved-comment.odt opens as ZIP and its content.xml parses independently. It contains two office:annotation elements, two matching annotation-end elements, creator/date fields and document paragraphs/styles. This establishes accessible comment structures for this fixture, not correct rendering of resolved-comment state, tracked changes, spreadsheets, macros or password-protected documents. (source), confidence high
• E2: It opens and saves Microsoft Office formats and exports to common interchange formats, though formatting loss is explicitly possible. (source), confidence high
• E3: ODF is a ZIP package containing XML files and can be inspected independently, but complete feature round-trip across formats was not tested. (source), confidence high
• E4: Documents can be saved to local paths or user-selected network locations without requiring a hosted account. (source), confidence medium
• E5: DoBackup_Impl first requires an existing source document and uses NameClash::OVERWRITE when transferring the backup; failure can set ERRCODE_SFX_CANTCREATEBACKUP. Internal transactional backups and a backup-restore error path also exist separately. A persistent backup is not necessarily an unlimited version history, and these branches do not establish crash durability or the user's configured backup/autorecovery policy. (source), confidence medium
• sovereignty: A positive Sovereignty finding requires established E1, E2 and E4 in the declared scope. The existing access/exit/custody record for LibreOffice (ODF) does not establish all three minimums. The prior positive finding is withdrawn; recorded storage and portability strengths remain facts, not a verified failure. (source), confidence medium
• longevity: E3 is not established for LibreOffice (ODF)'s existing essential-record scope. The previous Longevity finding is replaced by Not assessed, not a verified failure or a positive placeholder. (source), confidence medium
• locality: The office workflow can run and store documents locally. (source), confidence medium
• transparency: The positive control observations above do not yet establish whole-scope E5. The methodology requires that minimum before a positive Transparency and Control finding; the previous positive finding is therefore withdrawn to Not assessed, not changed to Does not meet. (source), confidence medium
• E3: The ODT fixture independently exposes comments and XML structure, but not equivalent resolved-comment rendering, tracked changes, spreadsheet formulas/macros or encrypted document recovery. Complete version- and format-specific document semantics were not reconstructed for the original office profile. (source), confidence medium
• E5: Persistent and transactional backup paths, overwrite behavior and error handling are established in source, but do not prove configured retention or crash durability. Macro/external-link authorization, save/format-loss decisions and correction of consequential document changes remain insufficiently covered. (source), confidence medium
• E2: The former E2 Pass does not establish usable migration of the full declared office records, including tracked changes, formulas, macros and structural meaning. Supported formats and acknowledged formatting loss are not a completed essential-feature comparison. (source), confidence medium

7. Migration and recovery

Native storage format: ISO/IEC 26300 OpenDocument XML (.odt/.ods).

Synchronization or runtime model: Local Filesystem.

Example export or inspection command (not verified against any particular version or data set): unzip -p document.odt content.xml | xmllint --format -

8. Architectural strengths

Established strengths and their scope are recorded in the evidence and assessment findings on this page.

9. Architectural limitations

• Independent ODT annotation parsing is not complete office-document rendering or formula/macro recovery.
• Backup replacement and transactional recovery paths are distinct; effective settings and failure outcomes remain unverified.

10. Assessment findings and remaining work

Verification scenario: Round-trip documents with tracked changes, formulas, comments, embedded objects, and scripts in an independent ODF reader.

What may invalidate an overconfident claim: Complex document fidelity varies; launch time and suite size are not sovereignty criteria.

Documentation starting point: https://www.libreoffice.org/discover/what-is-opendocument/

Evidence update: 23 October 2026

• Resolved: The published resolved-comment.odt opens as ZIP and its content.xml parses independently. It contains two office:annotation elements, two matching annotation-end elements, creator/date fields and document paragraphs/styles. This establishes accessible comment structures for this fixture, not correct rendering of resolved-comment state, tracked changes, spreadsheets, macros or password-protected documents. Source.
• Resolved: DoBackup_Impl first requires an existing source document and uses NameClash::OVERWRITE when transferring the backup; failure can set ERRCODE_SFX_CANTCREATEBACKUP. Internal transactional backups and a backup-restore error path also exist separately. A persistent backup is not necessarily an unlimited version history, and these branches do not establish crash durability or the user’s configured backup/autorecovery policy. Source.
• Open: Current ODT/ODS/DOCX/XLSX comparisons including tracked changes/formulas/macros, encrypted-package inspection, actual repeated saves and crash recovery, older versions and external dependencies. E5 needs macro/external-link authority, format/overwrite decisions, effective backup/autorecovery and usable correction limits.

Assessment follow-up: These bounded findings are incorporated into the evidence above. Eligibility and principle ratings are deliberately unchanged; their reconciliation and any blank-status fixes are deferred to the next pass. Reproduction details and retained inputs are in evidence/third-pass/batch-6/.

Human-readable criteria: Can a person preserve content, structure, links, metadata, and history in an independently readable form, then restore and edit it without a vendor account?

Rating reconciliation: 24 October 2026

E3 and E5 remain Not Verified for the existing declared scope. Longevity and Transparency and Control are Not assessed pending their required minimums. Sovereignty is also Not assessed because the required access/exit/custody minimums are not all established. The prior E2 Pass is withdrawn; its essential-record migration comparison remains incomplete. This is a targeted evidence decision, not a finding that the product fails. Existing E1, E4 and Locality findings were not re-certified.

Remaining: Current ODT/ODS/DOCX/XLSX comparisons including tracked changes/formulas/macros, encrypted-package inspection, actual repeated saves and crash recovery, older versions and external dependencies. E5 needs macro/external-link authority, format/overwrite decisions, effective backup/autorecovery and usable correction limits.

Next without installing locally: Collect representative synthetic ODT/ODS/native-interchange pairs, encrypted test documents with non-secret credentials and semantic manifests; inspect packages and reuse same-version macro/link/save/recovery evidence.

The individual decision and provenance are retained in evidence/rating-reconciliation/batch-7/. Overall: Insufficient evidence.

Individually reconciled in rating batch 7 on 24 October 2026. E3/E5 remain Not Verified for explicit missing coverage; dependent unsupported findings corrected. Previously resolved questions are retained, not counted again. E1/E4/Locality were not re-certified by this targeted review. The assessment procedure is described in the methodology.