# Funding, recognition, and attribution

Updated 2026-09-24.

## Purpose
Support messaging and project credit should be clear without changing the authority of technical documents. This guide connects the [funding principles](?page=community/funding-policy) with the [attribution notice](?page=legal/NOTICE).

## Where recognition belongs
Use the Foundation support page for current support arrangements and the attribution notice for founder credit. Release notes can acknowledge concrete contributions. Technical specifications should focus on requirements, rationale, and evidence rather than sponsor messaging.

## Founder acknowledgment
Use the established wording: **Founder of the OpenForex Project: Franklin Armah Sharp.** A fuller biography requires verified source material and should appear on a separate profile page rather than be inferred from this credit.

## Supporter acknowledgment
When a real arrangement is published, identify the contribution and any relevant conditions. Avoid wording that suggests endorsement, technical certification, or governance authority unless a separate record establishes it. Respect agreed privacy boundaries for individuals.

## Contribution records
For editorial and technical work, record the change, reviewed revision, and contributor attribution where appropriate. Shared authorship should not erase the provenance of foundational source material. A correction record should explain what changed rather than simply replacing names or dates.

## Current publication boundary
No payment program, sponsorship tier, or official intake destination is established by this guide. Link readers to the [support page](?page=foundation/support) for available information and to [governance](?page=seed-content/governance/overview) for decision responsibilities.