OpenForex / KNOWLEDGE
Home / OpenForex Standards
Knowledge base
2 min read Available as Markdown

OpenForex Standards

The working standards catalog of the OpenForex Society, the standard-setting core of the OpenForex Foundation.

Publication status

Published by the OpenForex Society, the standard-setting core of the OpenForex Foundation, as part of its established standards service to the open standards community.

Version

0.2.0

Last Updated

2026-09-24

Current catalog

DocumentStatusScope
TVX Neutrality Standard literatureRatified working standardMonetary neutrality and QASH architecture
OFS-Kernel 1.0.0Standards referenceDeterministic execution and evidence boundaries
TVX Formula 1.0.0Standards referenceValuation-method specification work
Oracle systemStandards referenceInput provenance and validation design
Audit and complianceImplementation guidanceEvidence and review expectations

OpenForex Standards are ratified, established, and maintained as an operational standards service to the open standards community. Their authority derives from the OpenForex Society. The references in this catalog document the working framework and its implementation responsibilities.

Publication lifecycle

A Draft may change substantially. Review indicates that a named revision has been submitted for structured assessment. Approved means an authorized decision record identifies the accepted text and its effective version. Deprecated material remains available for historical interpretation and should point to its replacement.

Reference articles explain the working Standard, while examples demonstrate particular relationships. Future amendments pass through the review lifecycle; that lifecycle does not place the established Standard back into draft status.

What belongs in a specification

A complete specification states its scope, terminology, input domain, behavior, errors, invariants, security considerations, and compatibility boundaries. It identifies the tests and evidence by which a claim can be checked. Requirements should say what an implementation must do, and separate that from commentary explaining why.

Change discipline

A correction that changes technical meaning requires review even if it looks editorial. A change to a formula, numeric policy, accepted input, or failure condition may invalidate previous results. Record the changed behavior and explain migration expectations before assigning release status.

Making a proposal

Start with an RFC, identify affected documents, and include a concrete before-and-after example. Reviewers should be able to evaluate the change without reconstructing a private discussion.

The governance model describes institutional responsibilities. The contribution workflow describes how to prepare evidence and publish an accepted revision.

Sources & citation

Material type
Project reference
Publisher
OpenForex Society
Source version
0.2.0
Source-stated update

OpenForex Society. “OpenForex Standards.” Version 0.2.0. https://openforex.io/?page=seed-content%2Fstandards%2Findex. Include your access date when citing.

Download the exact published Markdown
Text fingerprint (SHA-256)0d0abc264bfe25956a488ea9e666d389f18b6f3907e335cc0f69f445f57f0203

This identifies the downloadable text, not an independent approval or a permanent archived edition.

Referenced material (8)

Standards, implementation references and worked calculations identify their sources and publication status. Read our sourcing and corrections policy.

KEEP EXPLORING

Put the reading to work.

Accessibility settings

Adjust the display for comfortable reading. Changes apply immediately to every page.

Light and dark modes use high-contrast colors.

Preferences are saved only in this browser. Browser zoom remains available.