You or your agent decides whether to execute elsewhere, hand it to another executor, or ignore it.
0∞ / DECISION INFRASTRUCTURE
The control layer between intelligence and execution.
Evidence before action.
Bring a market hypothesis through evidence, opposition, Council, receipt, thesis, and bounded mandate before any executor can act.
OPINION ≠ TRADENO CUSTODYFAIL CLOSED
Authority must be earned.
THE CANONICAL PATH
Every opinion crosses the same boundary.
The source of intelligence can change. The authority path cannot.
A Council approval is not an order. Market revalidation, economics, policy, and execution state still decide whether action is permitted.
YOUR FASTEST PATH THROUGH 0∞
See it. Run it. Connect it.
A new developer should be able to understand the product before reading its internals.
Read the canonical construct: roles, Council, receipt, thesis, mandate, economics, refusal.
READ-ONLY PROOF ↗ 02 / RUNTry the runtimeCall the real bounded service in SHADOW or PAPER. No exchange write is performed.
NO-WRITE RUNTIME ↗ 03 / CONNECTIntegrate your intelligenceUse MCP, REST, or SDK. Bring role adapters. Receive and verify a portable mandate.
DEVELOPER PATH ↗THE FINAL RELATIONSHIP IS YOURS
Three ways to relate to execution.
The reasoning, Council, receipt, thesis, and mandate semantics stay identical. Only the executor changes.
An external execution system can inspect its scope, expiry, bounds, and provenance before deciding whether to honor it.
Where an authorized venue connection exists, execution is limited by the intersection of session permission, mandate, and venue capability.
AUTHORIZATION WITHOUT CUSTODY
Your venue remains yours.
The exchange or venue controls custody. You control delegation and authorization. 0-infinity controls execution eligibility. Your agent supplies intent and intelligence.
Binance is a current execution context, not the definition of the product. Testnet and LIVE availability remain separately gated.
START WITH THE CONSTRUCT