Step 1 · Define protection envelopes
Sentinels keep your USB.Trade positions inside the boundaries you mandate. Work through the on-screen prompts to translate governance policies into executable parameters covering health checks, leverage ceilings, and escalation flows.
- Choose default templates or craft custom policies per strategy (e.g., delta-neutral vs. directional).
- Set threshold triggers for LTV, funding rate drift, and venue risk signals that should fire alerts or actions.
- Map escalation logic—who approves interventions, who receives notifications, and which channels you prefer.
Screenshot placeholder: Policy template selection UI with threshold sliders.
Step 2 · Activate sentinel modules
USB.Trade ships modular services for monitoring, rebalancing, and emergency responses. Enable the components that match your mandate and validate them with dry-run drills before allowing live intervention.
- Enable health monitor, margin shifter, and borrow optimizer modules; review the actions each can trigger.
- Run simulations with historical data or shadow balances to make sure sentinels behave as expected.
- Finalize signer approvals so sentinel transactions can submit seamlessly while remaining auditable.
Screenshot placeholder: Module activation list with simulation toggle.
Step 3 · Review receipts and alerting
After modules are active, confirm that sentinels will surface the right context when they fire. The UI exposes delivery settings for receipts and alert severity—adjust them now so your downstream stakeholders know what to expect.
- Set the delivery channels for sentinel receipts (webhooks, dashboards, email) and verify sample payloads.
- Map severity levels to your incident cadence so high-priority actions escalate immediately.
- Log the finalized configuration (screenshots + exported JSON) in your internal runbooks for audits.
Screenshot placeholder: Sentinel receipt preview showing event payload.