01
Presentation boundary
This website is an isolated product presentation. It has no broker login, credential forms, order tickets or execution controls.
SECURITY & GOVERNANCE
Boundaries are a system feature.
Research, public presentation and execution have different responsibilities. Explicit authority and observable state keep those responsibilities legible.
BUILT ON EXPLICIT STATEBRX / SECURITY
01 / SEPARATION BY DESIGN
Public presentation. Private operations.
02
Explicit authority
A strategy signal does not grant permission. Risk, account identity and execution authority remain separate checks.
03
Research separation
Research results and dry-run previews remain distinct from production and broker outcome truth.
04
Read-only health surfaces
Operational observability describes state. Health views do not authorize execution or mutate risk.
05
No silent substitution
No silent broker fallback, account selection or translation between incompatible intent contracts.
06
Inspectable uncertainty
Uncertain mutation results remain visible for reconciliation and operator review, including after a restart.
03 / FAIL-CLOSED DESIGN
When BRINX doesn’t know, it doesn’t guess.
Ambiguous accountBLOCK
Unsupported symbolBLOCK
Stale evidenceBLOCK
Unknown routeBLOCK
Uncertain executionRECONCILE
Missing authorityBLOCK
Missing authoritative dataNOT_AVAILABLE
Cross-broker fallbackNONE
04 / GOVERNANCE
Risk is explicit. Approval is specific.
Risk is account-specific, venue-specific and versioned. Strategy evidence, risk approval and execution approval are distinct responsibilities.
Risk approval ≠
execution approval.
execution approval.
BUILT ON EXPLICIT STATE.Understand the system.
VIEW ARCHITECTURE