# Contribution guide

How to prepare a clear, attributable, and reviewable contribution to 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

## Start with a focused problem
Identify the page, behavior, or assumption you want to improve. Explain who is affected and provide a concrete example. Check related pages so the change improves the whole explanation rather than leaving contradictory guidance elsewhere.

Use an [RFC](?page=seed-content/rfc-proposals/index) for changes to methodology, standard behavior, or governance. Use a focused editorial patch for spelling, structure, examples, or broken references that do not change meaning.

## Prepare your change
1. Record the current page version and source revision if available.
2. Edit the source Markdown or relevant portal file.
3. Explain the proposed change and its evidence.
4. Preserve draft status unless an authorized decision supports a transition.
5. Update the revision date and cross-references.
6. Verify the rendered page and affected navigation.

The root content tree and shared-hosting package carry corresponding documents. Keep them synchronized when preparing a release. The [content structure guide](?page=docs/content-structure) explains paths and publication boundaries.

## What to include with a submission
Provide a short problem statement, the changed behavior or wording, supporting references, and verification results. For simulations, include inputs, method, precision, outputs, and limitations. For implementations, identify the tested revision and unsupported cases.

Only submit material you are entitled to share. Preserve existing attribution. Do not include secrets, private records, or externally sourced text without appropriate rights. This package's public availability should not be treated as a substitute for a published license.

## Review and publication
Editors assess readability and source quality. Domain maintainers review technical meaning. Standards and governance approval require the authorized process described in [governance](?page=seed-content/governance/overview). A review request can be returned for clarification without rejecting the underlying idea.

The public repository destination remains configurable on the [source page](?page=developer/repository). No claim is made that a submission has been sent by editing a local file.

## Final checks
Read the change as a new reader. Follow every new link. Confirm that examples are labelled, terms are defined, and claims match available evidence. Use the [workflow](?page=docs/contribution-workflow) for the publication record.