Documentation versions

How WarnFire labels current, preview, deprecated, and historical documentation.

WarnFire documentation is tied to a product release line. The version selector identifies the release that a page describes; it does not change your workspace or application version.

Page status

Every maintained page has a visible status:

• Verified means the behavior was checked against the implementation or an automated test on the date shown.
• Preview describes functionality that is available only in a pre-release build or is not yet generally available.
• Deprecated documents a supported compatibility path that should not be used for new integrations.
• Historical preserves a frozen record for an older release. Historical pages are not updated to match current behavior.
• Needs verification means the page has not completed the current code-versus-documentation audit. Treat it as provisional.

Planned features do not appear as current product behavior. They belong in release notes or explicitly labeled roadmap material.

Current and frozen editions

The unversioned documentation URL is the canonical edition for the current WarnFire release line. Before a later release becomes current, the previous edition is frozen under a versioned URL so existing customers can continue to read the documentation that matches their deployment.

Corrections to security or safety guidance may be backported to a frozen edition. Feature changes are not.

Topic tags and audience

Topic tags group related guides across sections. Audience labels identify whether a page is intended for responders, workspace administrators, integration developers, or billing administrators.