The Proviso architecture connects a commitment layer, market access, and reference data. Each dependency has a specific job and its own constraints.
THESIS TRADING / PROVISOMarket availability follows venue metadata. Review the instrument, session, and liquidity before confirming an action.
Contract permissions, token identity, and chain support must align before a route can be authorized. References to a venue do not imply a partnership.
Per-leg agreement, freshness, and explicit multiplier handling.
US session context, canonical assets, and corporate actions.
15-minute design cadence; provider remains to be selected.
Daily design cadence; vendor and exact coverage remain unresolved.
Bounded string matching, costed polling, self-trigger flags.
Lifecycle notifications and the later Telegram interface.
Wallet and Hyperliquid linking, rule writer, alert mode, and client-side sealing.
Hyperliquid execution, limits, stop workflow, and the 90-day tester.
Fair Copy, complete caller records, and disclosure history.
Robinhood Chain spot actions and Stock Token conditions.
Costed X-post polling and a Telegram interface.
Each capability depends on the account permissions, data coverage, and venue support it needs. Your workspace shows the state of each connection.
Inspect key permissions, funding routes, and what each connection is designed to permit.