NIJA Operator Quick Reference Cards
Two versions of a consolidated quick reference guide for NIJA trading bot operators.
π Available Versions
1. Markdown Version (Text-Based)
File: NIJA_OPERATOR_QUICK_REFERENCE.md
- β
Plain text format, easily viewable in any text editor
- β
Perfect for terminal/CLI environments
- β
Copy-paste friendly commands
- β
Searchable with grep/find
- β
Version control friendly
- β
Printable via markdown-to-PDF tools
Use when:
- Working in SSH/terminal environment
- Need to quickly search for commands
- Want to print a physical reference card
- Prefer simple text format
2. HTML Version (Styled with Icons & Color Coding)
File: NIJA_OPERATOR_QUICK_REFERENCE.html
- β
Beautiful visual design with color coding
- β
Icon indicators for different sections
- β
Interactive hover effects
- β
Responsive design (mobile/tablet/desktop)
- β
Color-coded by priority (red=emergency, orange=warnings, etc.)
- β
Easy to scan visually
- β
Can be opened in any web browser
Use when:
- Need quick visual reference
- Want color-coded priority indicators
- Training new operators
- Creating presentations or documentation
- Prefer visual organization
Color Coding:
- π΄ Red - Emergency (Kill Switch, Critical Alerts)
- π Orange - Warnings (Alerts, Monitoring)
- π΅ Blue - Status & Information
- π’ Green - Success, Snapshots, Metrics
- π£ Purple - Filters & Configuration
π Whatβs Covered
Both versions include comprehensive coverage of:
π¨ Emergency Kill Switch
- Activation methods (CLI, API, File System)
- Status checking
- When to activate
- Deactivation procedures
π Status Commands
- Account & balance status
- Trading system diagnostics
- Analytics & reports
- Profit status checks
π Alerts & Monitoring
- Critical alert thresholds
- Auto kill-switch triggers
- Safety tests
- Monitoring integration
πΈ Snapshots & Metrics
- Command Center 8 key metrics
- API endpoints for real-time data
- Performance snapshots
- Programmatic access
π Market Filters
- Filter thresholds (ADX, volume, spread, etc.)
- Market quality checks
- Python integration examples
- Default values
π― Operational Quick Actions
- Start/stop commands
- Environment configuration
- Trade veto reasons
- Common troubleshooting
π Analytics Tracking
- 11 entry reason types
- 19 exit reason types
- Signal type classification
- Data file locations
π Troubleshooting
- Bot wonβt start
- No trades executing
- Heartbeat failures
- API issues
β‘ Rapid Fire Commands
- Quick health checks
- Real-time monitoring
- Log viewing
- Safety test execution
π Quick Start
View Markdown Version
# In terminal
cat NIJA_OPERATOR_QUICK_REFERENCE.md
# Or open in editor
nano NIJA_OPERATOR_QUICK_REFERENCE.md
code NIJA_OPERATOR_QUICK_REFERENCE.md
View HTML Version
# Open in default browser (macOS)
open NIJA_OPERATOR_QUICK_REFERENCE.html
# Open in default browser (Linux)
xdg-open NIJA_OPERATOR_QUICK_REFERENCE.html
# Open in default browser (Windows)
start NIJA_OPERATOR_QUICK_REFERENCE.html
# Or simply double-click the file in your file explorer
Print to PDF
From Markdown:
# Using pandoc
pandoc NIJA_OPERATOR_QUICK_REFERENCE.md -o NIJA_Quick_Reference.pdf
# Using grip (GitHub-flavored markdown)
grip NIJA_OPERATOR_QUICK_REFERENCE.md --export NIJA_Quick_Reference.html
From HTML:
- Open in browser β Print β Save as PDF
- Use browserβs βPrint to PDFβ feature
- Professional quality with colors and icons preserved
The Quick Reference Cards consolidate information from:
EMERGENCY_KILL_SWITCH_QUICK_REF.md - Kill switch procedures
QUICK_REFERENCE.md - Railway deployment & features
ANALYTICS_QUICK_REFERENCE.md - Analytics commands
COMMAND_CENTER_README.md - Dashboard metrics
OPERATIONAL_SAFETY_PROCEDURES.md - Safety protocols
README.md - Main project documentation
π― Target Audience
- NIJA Operators - Day-to-day bot operation
- On-Call Engineers - Emergency response
- System Administrators - Health monitoring
- New Team Members - Quick onboarding
- DevOps Engineers - Deployment & troubleshooting
β±οΈ Target Response Times
The Quick Reference is designed to help operators achieve:
- Emergency Kill Switch: < 30 seconds (actual: < 5 seconds via CLI)
- Status Check: < 1 minute
- Health Assessment: < 2 minutes
- Troubleshooting: < 5 minutes to identify issue
π‘ Best Practices
- Keep accessible: Bookmark HTML version or keep terminal with markdown open
- Print physical copy: For emergency situations without computer access
- Review regularly: Familiarize yourself with commands before emergencies
- Update bookmarks: Add key API endpoints to browser bookmarks
- Test commands: Try emergency procedures in test environment first
- Share with team: Ensure all operators have access to both versions
π Updates
These Quick Reference Cards are current as of Version 7.2.0 (February 2026).
When NIJA is updated:
- Check for new commands in release notes
- Update both markdown and HTML versions
- Test all commands still work
- Verify API endpoints are current
- Update version numbers
π Customization
Markdown Version
- Edit directly in any text editor
- Add your own sections or commands
- Adjust for your specific deployment
HTML Version
- CSS variables at top of file for easy color changes
- Modify color scheme by editing
:root CSS variables
- Add/remove sections by editing HTML structure
- Responsive design works on all screen sizes
In case of critical emergency:
- Activate kill switch FIRST - Donβt investigate while bot is still trading
- Review logs -
tail -f logs/nija.log
- Check positions - Via broker UI (Kraken/Coinbase)
- Follow procedures - In
OPERATIONAL_SAFETY_PROCEDURES.md
- Document incident - For post-mortem analysis
β
Verification Checklist
Before relying on Quick Reference in production:
Last Updated: February 2026
Version: 7.2.0
Status: Production Ready β