01
GATEDeterministic safety gate
Model output cannot bypass backend validation, supported instruments, leverage rules, or exposure constraints.
07ZAINEX SYSTEM
CONTROLLED BY ARCHITECTURE
Safety is not a warning.It is the workflow.
ZAINEX places validation, deterministic limits, manual approval, mandatory stop loss, exposure checks, and idempotent transactions directly inside the product flow.
MANUALFinal trade approval
MANDATORYStop loss input
PAPERCurrent execution scope
SYSTEM STATUSVERIFIED
SECURITY
IDENTITY
RISK
APPROVAL
DECISION PIPELINEVALIDATION FIRST
DEFENSE IN DEPTH
Multiple controls protect the same decision.
Security is stronger when identity, validation, risk, state transitions, and accounting all enforce compatible rules.
02
IDENTITYSession isolation
Verified Google users receive separate ZAINEX identities, private paper accounts, wallets, and trading sessions.
03
APPROVALManual trade authority
The system proposes and calculates. The user explicitly confirms LONG, SHORT, or WAIT.
SYSTEM FLOW
Controls applied before, during, and after an action.
Each phase prevents a different failure mode - from unauthorized access to duplicate balance movement.
01
Authenticate
A verified Google identity establishes the user session.
02
Authorize
Private account and internal service tokens scope the request.
03
Validate
Risk, amount, exposure, and request structure are enforced.
04
Audit
Orders, transfers, strategies, and wallet events remain traceable.
The safest automation is the automation that clearly knows where its authority ends.
Enter ZAINEX