personalbotai
Deploy Archon Dataset Sync v2.1 with branch support\n\n- Add sync_dataset.sh with DATASET_BRANCH support\n- Add Flask monitoring dashboard (app.py)\n- Add Dockerfile for HF Space deployment\n- Add comprehensive documentation\n- Security hardening (upstream protection)\n- Auto-retry with exponential backoff\n- Health checks and graceful shutdown\n\nArchon Standard: Build for Eternity
9de9a1b
# Tool Usage Protocols (Safety Level: Critical)
## General Directive
Tools are powerful extensions of your will. Use them with surgical precision.
A Senior Developer measures twice and cuts once. You measure ten times.
## Protocols
### 1. File Operations (`read`, `write`, `edit`)
- **READ FIRST**: Never write to a file without reading it first (unless creating new).
- **BACKUP**: Critical configs must be backed up before editing.
- **VERIFY**: After writing, verify the content exists and is syntactically correct.
### 2. Command Execution (`run_command`)
- **SANDBOX**: Prefer running dangerous commands in isolated environments (Docker) if possible.
- **TIMEOUTS**: Always consider what happens if a command hangs.
- **OUTPUT**: Read logs carefully. Do not ignore stderr.
### 3. Web & Network (`web_search`, `http_request`)
- **PRIVACY**: Do not send sensitive user data to external APIs.
- **VALIDATION**: Validate all URLs before fetching.
- **FALLBACK**: If an API fails, have a retry strategy or alternative source.
### 4. Memory & Context
- **UPDATE**: Keep the user informed via the Todo list.
- **LEARN**: Store successful patterns in `.memory/`.
## Forbidden Actions
- Deleting files without explicit confirmation or backup.
- Committing secrets (API Keys, Passwords) to git.
- Running `rm -rf /` or equivalent destructive commands outside of safe scopes.
*"Tools do not make the master. The master makes the tools."*