Releases & configuration
Revenue-agent workloads are assembled from reviewed immutable inputs and require explicit, product-scoped endpoint configuration.
The operational hold still governs. Release and configuration contracts are documented for review; they do not authorize a deployment, live network, customer credential, or money-bearing action.
Immutable workload inputs
The revenue-agent image is assembled from an exact Node OCI digest and exact Debian package versions from a dated Debian snapshot. Its image build does not add floating package repositories, invoke pip, or install model-provider CLIs. The entrypoint removes ambient model-provider credentials before the agent starts and retains only product-scoped Stado credentials.
The release workflow packages the reviewed Dockerfile into a content-addressed Stado artifact. An existing release object is never mutated. Review records must bind the exact source commit, immutable image inputs, artifact identity, and release object rather than rebuilding from a moving branch.
Product-scoped trading endpoints
Solana, Jupiter, and price actions require all applicable HTTPS endpoints to be configured explicitly:
| Setting | Purpose |
|---|---|
TRADING_AUTONOMY_SOLANA_RPC_URL | Solana JSON-RPC service. |
TRADING_AUTONOMY_JUPITER_QUOTE_URL | Jupiter quote service. |
TRADING_AUTONOMY_JUPITER_SWAP_URL | Jupiter swap service. |
TRADING_AUTONOMY_PRICE_SERVICE_URL | Product price service. |
TRADING_AUTONOMY_SOLANA_NETWORK | Explorer-network label; defaults to mainnet-beta and never selects an RPC host. |
Endpoint configuration is non-secret. Values containing embedded credentials, query parameters, or fragments are rejected. Missing endpoint configuration fails client construction, so retained actions cannot silently fall through to a public provider.
Model-router boundary
Model-provider credentials belong only in Stado's model router, never in the trading product. Stado materializes STADO_MODEL_ROUTER_URL and STADO_MODEL_ROUTER_TOKEN into an agent workload from the exact wisent-trade-agent-model-router item. The product application does not receive the router bearer value.
Repository release manifests
| Product | Declared artifact |
|---|---|
trading-autonomy | A Linux AMD64 trading-autonomy-agent.pyz with version from VERSION, configuration and state schema 1, and no rollback-compatible versions. |
wisent-trade | A Vercel output archive and evidence/build.json, versioned from package.json and delivered with scoped Vercel project fields. |
These manifests preserve declared artifact provenance, but candidate or stable labels alone are not proof of operation and do not supersede the hold.