Not published by default
No win rate, profit, funded-account outcome or client return is inferred from technical status.
Proof should show
exactly what was verified.
Veeval separates engineering proof from trading-performance claims. A passing build, healthy service or recovered deployment is evidence of that specific mechanism—not evidence of guaranteed profit.
Not invented
Veeval should publish client or partner proof only when it is real, consented, scoped and attributable.
Mechanism proof
What the system is designed to do and which authority boundaries apply.
Technical proof
Build identity, tests, runtime health, rollback and restore evidence.
Operational proof
Real service continuity, incident/recovery evidence and support readiness.
Decision proof
Traceable Market Truth, evidence, governor state and canonical episode lifecycle.
Performance proof
Only real scoped results with source, period, limitations and methodology.
Client proof
Only real, consented client evidence with privacy-safe attribution.
CURRENT PRINCIPLE
Empty proof stays empty.
When real evidence is unavailable, Veeval should show the methodology, the verification state and the missing evidence instead of filling the space with a synthetic statistic, testimonial or success claim.