AttnomSolutions
Loading page
Bringing in the next surface without the heavy transition shell.
Loading page
Bringing in the next surface without the heavy transition shell.
Trading Bots / Free now
Allocate capital across Safe, Medium, and Hardcore bot modes with daily loss locks and runner health checks.
Access
Free now
Output
Mode allocation, Runner health, Loss lock
Best for
Multi-bot capital planning, risk-mode allocation, loss lock setup, and trading desk oversight.
The control center should own permissions, deployment state, approvals, emergency-stop authority, and broadcast policy changes across every live runner.
Fleet authority
Single authority
Operators can see who is allowed to run what, where, and under which guardrails.
Approval memory
Operator history
Changes should show owner, intent, and timing instead of behaving like silent config flips.
Broadcast policy
Risk patch ready
Operators need one place to push new caps, alerts, and kill behavior fleet-wide.
Launch flow
Step 1
Inspect which runners are live, paused, staged, or blocked before changing capital or permissions.
Step 2
Review lane ownership, approval cadence, and recent policy changes before arming new deployments.
Step 3
Broadcast updated risk policy, alert routing, or emergency controls from one central rail.
Step 4
Leave a visible approval trail whenever fleet controls change.
Desk capabilities
Emergency scope
Safe cap
$23,000
46.0% protected allocation
Core cap
$20,000
40.0% default execution lane
Hardcore cap
$7,000
14.0% aggressive ceiling
Loss lock
$1,400
2.8% fleet-wide daily stop
Approval cadence
6h
Live approval expires without renewed operator confirmation.
Emergency mode
FLEET
Primary stop scope for this operating window.
Fleet orchestration
Safe lane
2 runners
$23,000 ceiling with slower approvals and tighter kill sensitivity.
Core lane
2 runners
$20,000 for day-to-day execution under normal approvals.
Hardcore lane
1 runners
$7,000 only if live approvals and kill switch settings are current.
Authority board
Permissions
6h review
Live changes expire without explicit operator renewal.
Deployment state
3 live / 1 staged
Separate staged runners from live runners before issuing broadcast changes.
Emergency stop
fleet scope
The primary kill path should be obvious and role-aware.
Broadcast policy
Risk patch ready
Push revised caps, alert routes, and permissions fleet-wide from here.
Approval history
Broadcast cap update
Loss lock moved to 2.8% with 6h re-approval cadence.
Fleet ownership check
4 active runners require owner confirmation before live control changes.
Emergency controls
FLEET kill scope is primary until the next operator handoff.
Policy memory
Every policy push should carry scope, owner, time, and rollback note.