This page describes how content published on this site is produced and verified. It applies to blog articles, documentation pages, the glossary, and comparisons.
Who writes
Content is written by the team that designs and builds Obscura Flow. There are no guest authors and no outsourced writing. No content carries an individual author byline: pages commit the organization, not a person.
This page will be replaced by named author pages the day identified contributors sign the content. Publishing a fictional expert profile today to strengthen a credibility signal would be precisely what that signal exists to prevent.
Sources
Technical claims about Obscura Flow describe capabilities present in the released macOS application. A feature that is announced but not available is flagged as such, or is not mentioned.
Claims about formats, documentary standards, and preservation practice rely on the corresponding public specifications: EXIF, IPTC, XMP, Dublin Core, SHA-256, Ed25519. Where a practice reflects professional usage rather than a standard, the wording says so.
Writing rules
- A verifiable claim rather than a superlative. The words "leading", "revolutionary", and "best" are not used.
- No number without an origin. A percentage or duration without a measurable source is not published.
- No fabricated testimonials or case studies. A customer reference is published only with that party's agreement.
- Product limitations are written in the same place as its capabilities, not deferred to a separate page.
- A question has one answer across the whole site: FAQ entries come from a single shared source.
Use of AI in writing
Writing assistance tools may be used for formatting, translation, and proofreading. Every factual claim is verified by a team member before publication. No content is published without human review.
Comparisons
Pages comparing Obscura Flow to other software stay with observable capabilities. "Absent" means there is no equivalent built-in function, not that the task is impossible with that tool.
Every comparison includes a section describing where the other tool is the better choice. A comparison that won on every line would not be a comparison.
Product names and trademarks cited belong to their respective owners and are mentioned for identification purposes.
Corrections
A reported factual error is corrected at the source, across every affected page. Content does not display individual revision dates: articles carry their publication date, and the site's code is public in its version history.
To report an error, an imprecision, or a comparison you consider unfair, write to contact@obscuraflow.app or use the contact page.