Methodology · last reviewed 03 Aug 2026

Evidence before opinion

GenOffice.online is built to help readers verify a fast-changing alpha product. Every material claim is classified by provenance, checked against the closest available source, dated, and qualified where the source cannot establish real-world behavior.

Closer to the claim wins

A supplied URL is not automatically authoritative. We identify who published it, what it can establish, and whether a newer or more direct source exists.

  1. 01

    Official product and release material

    Product pages, repository files, release metadata, licenses, security notes, and maintainer documentation establish what the publisher currently says and ships.

  2. 02

    Primary standards and research

    Standards, specifications, and first-party technical records are used when a product claim depends on a format, protocol, legal term, or research result.

  3. 03

    Independent measurement

    Hands-on tests and benchmarks matter only when the build, configuration, inputs, date, method, and limitations are visible and reproducible.

  4. 04

    Practitioner and community reports

    Discussion can reveal questions, terminology, and failure modes. It does not replace a direct source for controlled facts.

  5. 05

    Editorial interpretation

    We connect the evidence to a decision, but label the result as interpretation rather than turning it into a synthetic fact.

Official

What the publisher says

Useful for version, scope, license, platform, architecture, and current product positioning. It is not independent validation.

Independent

What a reproducible test found

Requires a dated method and current artifact. This label is not used on the current site because no matching GenOffice alpha benchmark was found.

Editorial

How we interpret the evidence

Used for decision frames such as which product to test first. It is never presented as an endorsement or universal winner.

What gets rechecked

Release version, publication date, maturity label, download platforms, account requirements, pricing or credits, license boundary, and product capabilities can change quickly. A future update should verify each against the live official page and repository before changing copy.

How conflicts are handled

The newest source closest to the claim takes priority. If the product page and repository still conflict, both versions are reported with dates instead of being merged into a cleaner but unsupported answer.

Comparable dimensions, not point scores

Comparison pages use release posture, platform, editor scope, format support, AI path, license boundary, and the first workload test. They do not add unlike qualities into a score or name a winner without a declared workload.

Correct the closest claim and its downstream uses

A correction should identify the exact claim, provide the stronger source, record the check date, and update every page, FAQ, table, schema field, and metadata description that depends on it. Silent changes are avoided when the correction materially changes a reader's decision.

Material claims on the homepage

Sources supporting material claims on this page
ClaimSourceClassChecked
GenOffice is currently presented as alpha software.Maturity is time-sensitive; confirm again before installing.Official GenOffice pageOfficial
The reviewed desktop release is v0.4.110 for macOS Apple Silicon and Windows x64.The release was published on August 2, 2026.Official v0.4.110 releaseOfficial
The suite repository describes Docs, Sheets, Slides, PDF, and Shell apps sharing an engine layer.This is maintainer documentation, not an independent runtime test.Official repository READMEOfficial
The repository is Apache-2.0 except for the separately licensed ee directory.Do not describe the entire repository tree as uniformly Apache-2.0.Repository license sectionOfficial
AI model calls are documented as using a Genspark account and the Genspark service.The official page states that AI features consume Genspark credits.Official repository READMEOfficial