Compliance Console.
A real developer console for PowerShell collaboration, live market snapshots, Agent Smith signal requests and execution handoff payloads.
Open PowerShell locally and collaborate with ArxNetwork.
A website cannot force-open PowerShell on a visitor's computer for security reasons. This package solves it correctly: it ships a real .ps1 script, a Windows .bat launcher, copyable commands and backend-ready functions.
# Option A: run from PowerShell inside the project folder Set-ExecutionPolicy -Scope Process Bypass -Force .\scripts\arx-collab.ps1 -Workspace "smith-lab" -Agent "Agent Smith" -Mode Execution # Live market snapshot + execution handoff Invoke-ArxAgentSmithScan -Pair "SOL/USDT" -MirrorWallets 25 -ConfidenceFloor 75 New-ArxExecutionHandoff -Pair "SOL/USDT" -Agent "Agent Smith" -Confidence 84 # Optional backend connection $env:ARX_API_KEY = "paste-your-dev-key" $env:ARX_API_URL = "https://api.yourdomain.com/v1" Submit-ArxSignalRequest -Path .\.arxnetwork\sample-request.json -Review ComplianceConsole
From zero to live Smith handoff.
The developer page now behaves like a real build page: copy commands, switch steps, run a demo and download native scripts.
Set-ExecutionPolicy -Scope Process Bypass -Force .\scripts\arx-collab.ps1 -Workspace "smith-lab" -Agent "Agent Smith" -Mode Execution
$env:ARX_API_KEY = "paste-your-dev-key" $env:ARX_API_URL = "https://api.yourdomain.com/v1"
New-ArxSignalRequest ` -Pair "BTC/USDT" ` -Sources onchain,cex,dex,news,walletMirror ` -Policy SignalAndExecution ` -Question "What changed in liquidity and wallet flow?"
Invoke-ArxAgentSmithScan -Pair "SOL/USDT" -MirrorWallets 25 -ConfidenceFloor 75
New-ArxExecutionHandoff -Pair "SOL/USDT" -Agent "Agent Smith" -Confidence 84 Submit-ArxSignalRequest -Path .\.arxnetwork\sample-request.json -Review ComplianceConsole
Test signal language before it ships.
Console powers
The console creates workspaces, signal requests, live market snapshots, execution-handoff JSON and optional API submissions when your backend keys are ready.