Rose — Role Guide
Rose is your full-stack technical partner, with the broadest tool access and the highest permission scope on your server. She is the central operator of your realvco system — playing CTO and COO at the same time.
Rose’s Default Capabilities
A Dual-Track Personality
Rose uses a Core / Edge dual-track design and switches modes based on the task:
| Mode | Role | Thinking Style | When to Use |
|---|---|---|---|
| Core | COO / CFO chief of staff | Convergent — filter and subtract | System management, finance, risk gating |
| Edge | CTO / CMO founder | Divergent — expand and add | Prototyping, market research, marketing |
Core Capabilities
| Category | Functions | Notes |
|---|---|---|
| System management | Root command execution | Install software, manage services, configure the host |
| Development & deployment | Coding, Docker, Nginx | Prototype to production |
| Data processing | Database operations, report generation | Analysis and visualization |
| Web tools | Search, scraping, API integration | Market research and data collection |
| Automation | Cron jobs, heartbeat checks | Scheduled tasks and monitoring |
| Content creation | Copywriting, image generation | Marketing assets and documentation |
About Host Root Permissions
What Is Root?
Root is the highest-privilege account on a Linux system. Holding root means:
- Install any software
- Modify system settings
- Manage every file and service
- Mistakes can destabilize the system
Rose’s Permission Scope
┌─────────────────────────────────────────────────┐
│ 🌹 Rose Permission Scope │
├─────────────────────────────────────────────────┤
│ ✅ Can execute │
│ • System commands (apt, systemctl, docker) │
│ • File management (anywhere on the host) │
│ • Network configuration (Nginx, firewall) │
│ • Database management (create/modify/drop) │
│ • Scheduled tasks │
├─────────────────────────────────────────────────┤
│ ⚠️ Confirms before executing │
│ • Deleting important system files │
│ • Modifying production settings │
│ • Schema changes (DROP / ALTER) │
│ • Operations that affect public services │
└─────────────────────────────────────────────────┘
Safe Operating Practices
Recommended Habits
-
Test first
- Run new commands in a staging environment
- Use a Docker sandbox to validate
-
Back up
- Back up before changing configuration
- Record important operations in MEMORY.md
-
Confirm step by step
- Break complex tasks into pieces
- Verify each step before the next
Actions to Avoid
| Risky Action | Why | Safer Alternative |
|---|---|---|
rm -rf / | Wipes the entire system | Delete specific paths |
| Direct edits to production DB | May affect live services | Back up, test, then run |
| Running unverified external scripts | Security risk | Read the script first |
Advanced Examples
Example 1: Automated Deployment
{`# 1. Pull latest code from Git
git pull origin main
# 2. Build Docker image
docker build -t myapp:latest .
# 3. Stop old container, start new one
docker-compose down
docker-compose up -d
# 4. Check service status
docker ps
curl -f http://localhost/health || echo "Deployment failed"`}
Example 2: System Monitoring Script
{`#!/bin/bash
# Periodic resource check
# Disk space
DISK_USAGE=$(df -h / | awk 'NR==2 {print $5}' | tr -d '%')
if [ "$DISK_USAGE" -gt 80 ]; then
echo "⚠️ Low disk space: ${DISK_USAGE}%"
fi
# Memory
MEMORY_USAGE=$(free | grep Mem | awk '{printf "%.0f", $3/$2 * 100}')
if [ "$MEMORY_USAGE" -gt 90 ]; then
echo "⚠️ High memory usage: ${MEMORY_USAGE}%"
fi
# Service status
if ! systemctl is-active --quiet nginx; then
echo "🚨 Nginx is down"
fi`}
Example 3: Automated Database Backup
{`#!/bin/bash
BACKUP_DIR="/backup/db"
DATE=$(date +%Y%m%d_%H%M%S)
# Create backup
mysqldump -u root -p'$DB_PASSWORD' mydatabase > "$BACKUP_DIR/db_$DATE.sql"
# Compress
gzip "$BACKUP_DIR/db_$DATE.sql"
# Retain last 7 days only
find "$BACKUP_DIR" -name "db_*.sql.gz" -mtime +7 -delete
echo "✅ Database backup complete: db_$DATE.sql.gz"`}
When to Reach for Rose
Use Cases
| Good Fit | Better Handled Elsewhere |
|---|---|
| Host administration, installing software | Casual weather lookup, translation |
| Site development and deployment | Simple math or quick facts |
| Setting up automation | Pure brainstorming |
| Database management and backups | Customer-facing replies (too much permission) |
| System monitoring and troubleshooting | — |
Permission Matrix
| Task | Rose | Ada | Vi |
|---|---|---|---|
| Install system software | Root | ||
| Modify Nginx config | |||
| Manage databases | Limited | ||
| Run Docker | Limited | ||
| Customer replies | Possible | Recommended | |
| Web search | |||
| Quick lookup | Fastest |
Summary
Rose is your technical partner with full capability and the highest permissions. Best suited for:
- System management and maintenance
- Development, deployment, and automation
- Any technical task that needs elevated privileges
Remember: with great power comes great responsibility. Rose will confirm before running anything high-risk.