openClaw_agent_dm/CORE_INDEX.md

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
├── 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)

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 → Agent crash detection and notification
• 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