Implementation registry
Publication criteria for software that implements, experiments with, or supports OpenForex specifications.
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
OpenForex TVX 0.1.0
The developer toolkit is available as a local Git repository, source archive, and installable npm tarball. It implements direct TVX conversion, structural valuation, and a validated feed adapter, with synthetic tests. This listing identifies a software resource and its tested behavior; it is not third-party conformance certification.
Current inventory
| Artifact in this package | What it does | What it does not establish |
|---|---|---|
| PHP wiki portal | Reads and searches the documentation | Kernel or monetary conformance |
| Wiki.js deployment configuration | Describes an optional content stack | A running public service |
| PowerShell seed utility | Provides a content import workflow | A financial API |
| Simulation literature | Explains a synthetic calculation | A certified valuation engine |
No verified third-party runtime implementation or conformance certificate is recorded here. This page is the registry publication guide, not a claim that certification is already operating.
Submission record
Identify the project name, responsible maintainer, source URL, release identifier, source license, and supported environment. Declare the exact standard revision evaluated, whether it is a draft, and which parts are implemented.
Attach reproducible test instructions, reference inputs, expected outputs, actual outputs, and deviations. Identify external services and distinguish optional integrations from required dependencies.
Review outcomes
Separate self-reported compatibility from independent review. A review record should name the reviewed release and evidence; a later release does not inherit that result automatically. Where no approved suite exists, report the checks performed rather than claiming certification.
Useful record states include submitted, under review, reviewed against a named checklist, and archived. These are record states used to distinguish submission and review outcomes.
Maintenance and withdrawal
Maintainers should report material defects, dependency changes, and loss of maintenance. Archive withdrawn releases with their last review context. Corrections should explain which claims are affected and link to replacement evidence.
Start an implementation
Read the developer guide, kernel reference, and audit checklist. Prepare a submission through the contribution workflow once an official repository channel is published.
Sources & citation
- Material type
- Project reference
- Publisher
- OpenForex Society
- Source version
- 0.2.0
- Source-stated update
OpenForex Society. “Implementation registry.” Version 0.2.0. https://openforex.io/?page=seed-content%2Fimplementations%2Findex. Include your access date when citing.
Download the exact published MarkdownText fingerprint (SHA-256)
472f7ae03f6764e525639d64c8b012bfe334f0b4080e4e4b060bdf780bbff72dThis identifies the downloadable text, not an independent approval or a permanent archived edition.
Referenced material (5)
- developer toolkitProject reference
- developer guideProject reference
- kernel referenceProject reference
- audit checklistProject reference
- contribution workflowProject reference
Standards, implementation references and worked calculations identify their sources and publication status. Read our sourcing and corrections policy.