Early Access game documentation has a versioning problem. A value that is correct today may change after the next patch, while an unverified player report can spread faster than an official explanation. When I started building an independent guide for Fatal Frontier 1869, the hard part was not producing more pages. It was deciding what each statement was allowed to claim.

This article describes the content model I use for the project. It is useful for any small documentation site that covers a fast-changing product.

Treat confidence as data

Every important claim belongs to one of four buckets:

Official — stated by the developer, an official FAQ, Terms page, store listing, or patch note.

Observed — reproduced in the current game build or confirmed through a repeatable check.

Reported — described by players, but not independently reproduced.

Unknown — a useful question whose answer is not yet supported.

The fourth state matters.…