# Build with OpenForex

A practical entry point for documentation contributors, application developers, and researchers examining OpenForex.

## 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

## Choose a workstream
| Workstream | Starting point | First useful deliverable |
| --- | --- | --- |
| Documentation | [Contribution guide](?page=seed-content/developers/contribution-guide) | A focused correction with references |
| Portal development | [Portal operations](?page=docs/wiki-portal) | A reproducible reading or navigation fix |
| Method research | [TVX standard](?page=seed-content/tvx-formula/1.0.0) | A derivation with assumptions |
| Kernel prototyping | [Kernel reference](?page=seed-content/ofs-kernel/1.0.0) | A replayable, explicitly experimental calculation |
| Data research | [Oracle design](?page=seed-content/oracle-system/index) | A provenance-rich sample snapshot |

## Run the documentation portal
In the XAMPP workspace, start Apache and open the project through localhost. The root entry point loads the shared PHP reader; Markdown is read directly from content directories. No database or compilation step is required for article reading.

For another host, use the [shared-hosting guide](?page=docs/shared-hosting-architecture). The [architecture overview](?page=docs/architecture) distinguishes this reader from the optional Wiki.js stack.

## Understand the API boundary
The [API reference](?page=developer/api) concerns Wiki.js content management. This package does not implement conversion, issuance, balances, payments, or settlement endpoints. A runtime API needs a reviewed design, authentication model, and error contract.

## Before publishing a prototype
Pin the specification revision, capture inputs, document numeric behavior, and list unsupported cases. Mark experimental results clearly. Keep them distinct from approved standards or live financial activity.

## Source and collaboration
The [repository page](?page=developer/repository) explains source structure and the public destination's status. Prepare focused patches with a problem statement, changed behavior, and supporting evidence.

Read the [registry criteria](?page=seed-content/implementations/index) before making compatibility claims. Use an [RFC](?page=seed-content/rfc-proposals/index) when a change alters standard behavior or governance.