# Documentation page template

Use this structure when preparing a new explanation, technical draft, or proposal. This is an authoring tool; its example fields do not claim approval or appoint maintainers.

## Title and purpose
Choose a specific title. Open with a paragraph explaining the reader's question, the page's scope, and its relationship to existing literature.

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

## Ownership and sources
Identify an accountable author or maintainer only when that assignment is real. Cite the foundational or technical sources used, including their versions. Distinguish source claims from the author's proposals.

## Main explanation
Define the relevant terms and assumptions. Explain responsibilities, inputs, behavior, and outputs in the order the reader needs them. A technical page should state invalid cases and limitations as well as successful behavior.

## Worked example or evidence
Show a concrete example with units and reproducible steps. Label synthetic inputs clearly. State what the example demonstrates and what it cannot establish. Link supporting artifacts when available.

## Open decisions
Name unresolved questions precisely. Explain the evidence needed to resolve them. Do not insert invented parameters, approvals, committee appointments, or operational claims to fill gaps.

## Related reading and revision record
Link the most useful next pages. Summarize substantial changes and the reason for them. Preserve historical context when correcting a technical claim.

Use the [contribution guide](?page=seed-content/developers/contribution-guide), [content conventions](?page=docs/content-structure), and [RFC process](?page=seed-content/rfc-proposals/index) to prepare a reviewable submission.