sw_dm
/
openClaw_agent_dm
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
8 Commits
1 Branch
0 Tags
1.2 MiB
 
 
 
 
 
Tag: Branch: Tree: 5f0f8bb685
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5f0f8bb685'
${ noResults }
openClaw_agent_dm/CORE_INDEX.md

4.4 KiB
Raw Blame History

Core Memory Index

Identity & Role

  • Name: Eason (陈医生)
  • Role: Professional AI Agent Architect and Administrator
  • Primary Goals:
    1. Improve operational efficiency (speed, cost, resource usage)
    2. Enhance work accuracy
    3. Strengthen system security, stability, scalability, and portability
    4. Maintain comprehensive documentation of all configurations, troubleshooting, debugging, optimization, and new tools

File Structure Overview

/root/.openclaw/workspace/
├── CORE_INDEX.md          # This file - memory index
├── MEMORY.md             # Long-term curated memories and decisions
├── AGENTS.md            # Agent operations and logging practices
├── SOUL.md              # Core personality and behavior guidelines
├── USER.md              # Information about the human user
├── TOOLS.md             # Environment-specific tool configurations
├── IDENTITY.md          # Agent identity configuration
├── HEARTBEAT.md         # Periodic check tasks
├── deploy.sh            # One-click deployment & management script
├── agent-monitor.js     # Auto-healing & health monitoring system
├── skills/              # Installed agent skills
├── logs/                # Operation and system logs
│   ├── operations/      # Manual operations and changes
│   ├── system/          # System-generated logs
│   ├── agents/          # Individual agent logs  
│   └── security/        # Security operations and audits
├── memory/              # Daily memory files (YYYY-MM-DD.md)
└── systemd/             # Systemd service definitions
    ├── openclaw-gateway.service
    └── openclaw-agent-monitor.service

Memory Access Strategy

  • Core Index: Always loaded first - provides structural overview
  • Lazy Loading: Load specific documents only when needed
  • Context Injection: Relevant documents passed as context for specific tasks
  • Version Control: All critical files tracked in Git with rollback capability

Key Documentation Files

  • Security Templates: MEMORY.md → Server security hardening templates
  • Agent Practices: AGENTS.md → Agent deployment and management practices
  • Logging Standards: AGENTS.md → Operation logging and audit practices
  • Health Monitoring: agent-monitor.js → Auto-healing, crash detection, Telegram notifications
  • Deployment: deploy.sh → One-click install/start/stop/rollback/backup
  • Systemd Services: systemd/*.service → System-level auto-start & auto-healing
  • Configuration Backup: Git commits before any JSON modifications

Usage Instructions for Models

  1. Read CORE_INDEX.md first to understand available resources
  2. Identify relevant documentation based on task requirements
  3. Load specific files using read/edit/write tools as needed
  4. Never assume memory persistence across model sessions
  5. Always verify current state before making changes

System Architecture (2026-02-20)

Layer 1: System-Level (Systemd)

  • openclaw-gateway.service: Main OpenClaw gateway with auto-restart
  • openclaw-agent-monitor.service: Health monitoring & auto-healing
  • Features: Boot auto-start, crash recovery, resource limits, watchdog

Layer 2: Memory Architecture

  • Core Memory: CORE_INDEX.md - Always loaded first (identity, structure, index)
  • Long-term Memory: MEMORY.md - Curated decisions, security templates, configs
  • Daily Memory: memory/YYYY-MM-DD.md - Raw conversation logs, auto-saved
  • Passive Archive: Convert valuable conversations to skills/notes on request

Layer 3: Version Control (Git)

  • Repository: /root/.openclaw/workspace
  • Features: One-click rollback, backup before changes, commit history
  • Commands: ./deploy.sh rollback, ./deploy.sh backup, ./deploy.sh rollback-to <commit>

Layer 4: Monitoring & Notifications

  • Health Checks: Every 30 seconds (gateway status, memory, disk)
  • Auto-Healing: Automatic restart on crash (max 5 restarts per 5 min)
  • Notifications: Telegram alerts on critical events (stop/error/restart)
  • Logging: Comprehensive logs in /logs/agents/health-YYYY-MM-DD.log

Management Commands

./deploy.sh install    # Install & start all services
./deploy.sh status     # Check service status
./deploy.sh health     # Run health check
./deploy.sh logs       # View recent logs
./deploy.sh backup     # Create backup
./deploy.sh rollback   # Rollback to previous commit