Asset onboarding
Name the asset and its IBKR sub-account. Everything derivable is derived here; what is left is named, in order, with the command that does it.
Authenticate to read the routes a new asset can inherit shared policy from.
Plan
—Derived configuration
Install it with tools/apply-route-config.mjs, never by hand. The full-fill capability, the limit price and every deployment address are deliberately absent: each belongs to this asset alone.
Run it
Save the descriptor, then drive the whole ladder from one command. It stops at the first stage that needs a human and says which.
Deployment runs from the host as an operator, never from this page: the deployment admin does not enter the hosted runtime, and a web request must not be able to create a contract.
What this page cannot do
- It cannot review. The full-fill capability, the limit price and the credit limit are dated human assertions about one account and one contract id. Deriving them from another asset is how one asset trades on another's authority.
- It cannot deploy. Five of the asset's contracts bind each other immutably, so each asset needs its own; the keys that create them are not readable from here.
- It does not prove readiness. A complete ladder means every check passed against the evidence read at that moment, not that the next order will fill.