Knowledge Status and Source Policy

This page is the interpretation policy for Orvex documentation. It is updated with the documentation release and should be read before relying on a number, address, reward, or launch statement.

Lifecycle labels

Every factual statement belongs to one of these states:

Label	Meaning	How an assistant should answer
Live	Deployed, published, and intended for current use	State it as current and link the source page.
Planned	Intended for a future release or launch phase	Say that it is planned; do not describe it as available now.
Illustrative	An example used to explain a mechanism	Never present the example as an active parameter.
Deprecated	Retained only to explain an older behavior	Say that it is no longer current and prefer the replacement.

If a page does not explicitly state a lifecycle label, use the page's launch-status language. Words such as “pre-launch,” “will,” “upcoming,” “not yet,” “illustrative,” and “to be finalized” mean the claim is not a live production fact.

Current release status

As of the orvex-docusaurus documentation release on 2026-07-24:

• Orvex documentation targets Robinhood Chain.
• The roadmap describes Orvex as pre-launch for the token economy and governance.
• ORVX, oORVX, veORVX, and bveORVX parameters must be treated as planned unless a page publishes a deployed address and current parameter.
• Contract addresses published in Contract Addresses are the address source of truth. Verify each address on the Robinhood Chain explorer before signing.
• Reward rates, emissions, gauge weights, and APRs are not guaranteed by documentation.

Source precedence

When two pages appear to disagree, use this order:

1. A deployed contract and its verified explorer state.
2. The current Contract Addresses page.
3. A page labeled Live with a specific update date.
4. A page labeled Planned or Illustrative only for future design context.

Do not resolve an unknown value by guessing. The correct answer is “not published” or “planned” until an official source supplies it.

RAG answer policy

Answers generated from this documentation should include the lifecycle state when it changes the user's decision. For example: “The 30% strike is an illustrative design value, not a confirmed live parameter.” A missing address, reward rate, or launch date must remain explicitly missing rather than being inferred from an example.