Proof over trading hype.

Veeval is designed to report gold-trading outcomes as traceable lifecycle records rather than cherry-picked screenshots, unsupported bot claims or guaranteed-return marketing. Public performance evidence is shown only when its source, mode, scope and context can be validated.

EXAMPLE RECORD FORMAT

XAUUSD Decision Passport

DEMONSTRATION ONLY · NOT LIVE TRADING
WATCHREADYCLOSED
01WATCH

Potential XAUUSD setup observed; evidence is still being assembled.

02ARMED

A setup exists but activation requirements are not yet complete.

03READY

Timing, Market Truth and deterministic risk conditions align.

04ENTRY_NOW

The governed lifecycle reaches its time-sensitive entry state.

05RUNNING

A real activated trade is managed through the canonical lifecycle.

06CLOSED

Outcome and management evidence are retained for replay and learning.

WAIT, MISSED, NO_TRADE and INVALIDATED are also valid governed outcomes. A setup does not need to become a trade for the evidence trail to be useful.

Trust the evidence.
Not a sales screenshot.

Veeval separates what is live, what is an illustration, and what still needs genuine client evidence. Nothing is promoted just because it would look persuasive.

LIVE PUBLIC PROOFVERIFIABLE NOW

Exact build identity

CHECKING
Git headChecking…
BranchChecking…
Cloudflare buildChecking…
Observed build timeChecking…

Veeval is checking `/release.json`. If release identity cannot be verified, this panel stays unavailable rather than guessing.

ILLUSTRATIVE CLIENT JOURNEYNOT A TESTIMONIAL

See the access path before you start it.

This is an example of the governed workflow. It is not presented as a real customer story, profit result, endorsement or account outcome.

  1. 01
    Request

    Name + email starts the governed access request.

  2. 02
    Telegram

    The client continues through Veeval Telegram for account guidance.

  3. 03
    Verification

    IB/account eligibility is verified before protected access is granted.

  4. 04
    Released access

    Only products that are actually RELEASED and eligible can be delivered.

CLIENT PROOF STANDARDREAL PROOF ONLY

When customer proof appears, it must be genuine.

Client stories, testimonials, account outcomes and partner claims can appear only when the underlying evidence is real, consented, privacy-safe and scoped to what actually happened.

  • Real source and date
  • Consent and privacy boundary
  • Account mode and product version
  • No invented profit, win-rate or client-count claims
See the proof standard →
Verify first. Then decide.Requesting access does not enable broker execution or guarantee eligibility.
Request Veeval access →

Every performance claim should
carry its context.

Veeval separates live trading, demo validation, backtests and research evidence instead of presenting them as equivalent.

Source labelled

Live, demo, strategy-tester, backtest and research records are clearly identified.

Lifecycle preserved

Signal identity, entry, stop loss, take-profit management, invalidation, close and timing states remain part of the record when genuinely present.

No fabricated metrics

Until validated production evidence exists, Veeval does not invent win rates, client counts, profit figures or bot performance.

Gold trading bots should be judged on more than screenshots.

Useful evaluation needs the strategy version, environment, date range, costs, drawdown, risk settings, trade count and whether the evidence came from a real account, demo account or historical simulation. Veeval’s proof system preserves these distinctions before public claims are published.

Public bot proof remains evidence-gated.

The current Veeval Capability & Claims Register classifies Gold Master Mind and Next Gen as NOT VERIFIED. That does not mean their source is broken, and it does not mean they are production-ready. It means the current public proof gate is still missing one or more required pieces of exact evidence such as source identity, compile result, EX5 hash, release state, warning record or licence contract.

Veeval Gold and the Client Hub are classified as PILOT, with their own entitlement, account, release and authority requirements. These states can change only when the governed capability register and supporting evidence change.