Release identity
The public Website exposes its exact deployed Git head, branch, Cloudflare build UUID and observation time through /release.json.
TECHNICAL VERIFICATION RECORD · VEEVAL VERIFICATION CENTERVerify what passed.
Verify what passed.
See what it does not prove.
Veeval keeps release identity, engineering checks, runtime acceptance, decision evidence, performance evidence and client proof separate. One passing layer never silently certifies another.
LIVE PUBLIC RELEASE
CHECKINGVerify the build you are actually viewing.
Git head
Checking…BranchChecking…
Cloudflare build
Checking…Observed build timeChecking…
Veeval is checking `/release.json`. If release identity cannot be verified, this panel stays unavailable rather than guessing.
TRUST CENTERSix proof surfaces.
Six proof surfaces.
No synthetic certainty.
The public site shows only evidence it can truthfully support. Protected runtime and client evidence stays protected until a privacy-safe publication contract exists.
Technical verification
Veeval-issued verification can pass only for exact scoped evidence. Missing, stale or mismatched evidence remains visible instead of being promoted.
Methodology
Market Truth, evidence, independent analysis, governance and Decision Passport remain distinct layers with explicit authority boundaries.
Status & incidents
Public delivery status is separated from protected owner/runtime operations. A public page never invents private service health it cannot observe.
Privacy & security
Public proof avoids secrets, broker passwords and private client data. Technical evidence is published only at a privacy-safe scope.
Results & customer voice
Performance and client claims require real source, scope, consent and limitations. Empty evidence stays empty.
Not published by default
No win rate, profit, funded-account outcome or client return is inferred from technical status.
Not invented
Veeval publishes client or partner proof only when it is real, consented, scoped and attributable.
PROOF LAYERSVerification has
Verification has
different meanings.
Build health, runtime continuity and performance are intentionally separate evidence classes.
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.
V1 TECHNICAL VERIFICATION
Veeval-issued, exact-scope and fail-closed.
The V1 Technical Verification Record is not external certification and does not guarantee profitability. C21, C26 and genuine client/owner evidence cannot be simulated, shortened, backfilled or waived. Missing, stale or mismatched evidence prevents PASS.
CURRENT PRINCIPLE
Empty proof stays empty.
When evidence is unavailable, Veeval shows the method, state and missing requirement instead of filling the space with a synthetic statistic, testimonial, uptime claim or performance result.
EXPLORE THE EVIDENCE MODEL