How it works
From a question to a governed, streamed response.
The current experience uses a server-side frontier model while keeping provider credentials, model routing, usage limits, and current-data boundaries outside the browser.
1. Begin with a question
Ask about political or geopolitical developments, market transmission paths, exposed asset classes, scenarios, uncertainty, or invalidation conditions. Conversation context remains in the current browser session only.
2. Reserve usage and invoke the governed model route
The server validates the request, reserves public usage, verifies the Ask service identity, authorizes the conversational capability, and then invokes the configured model. The browser cannot choose a provider or see the provider credential.
3. Present the reasoning structure
The response streams as it is generated. A useful reading order is: what is known from the question, why it could matter, which assumptions connect the pieces, where uncertainty remains, and what would invalidate the scenario.
4. Keep the boundary visible
The beta labels its current-source boundary and does not turn a response into an action. It does not save the conversation, place a transaction, or connect to a trading system.