charlie-workspace

Summary

Charlie's Admin Workspace is a focused OpenClaw setup for managing, monitoring, and extending the daily operations of eMan and Meg's projects. It provides agent documentation, memory files, local tools, and project pipeline scripts to support seamless coordination and efficient task execution.

Included Assets

• Agent configuration and identity:
  • AGENTS.md, SOUL.md, IDENTITY.md, USER.md
• Workspace memory:
  • memory/YYYY-MM-DD.md, MEMORY.md, HEARTBEAT.md
• Operational tools and skills:
  • TOOLS.md, skills/charlie-csl/README.md, bin/charlie-csl.sh,
    skills/mission-control/SKILL.md, skills/qwen-local/SKILL.md, skills/qwen-local/agent-fallback.sh, skills/qwen-local/fallback-runner.sh
• Pipeline and logs:
  • docs/CHARLIE_SYSTEM_LOGS.md, docs/MISSION_CONTROL_TRAINING.md, docs/PIPELINE.md
• OpenClaw integration:
  • openclaw.json, .openclaw/workspace-state.json

How to Use

1. Initialize workspace context:

   • Review SOUL.md, IDENTITY.md, USER.md for agent identity and user background.
   • Check recent memory files (memory/YYYY-MM-DD.md) for context.

2. Project workflow:

   • Follow the 9-step Mission Control pipeline outlined in docs/PIPELINE.md and docs/MISSION_CONTROL_TRAINING.md.
   • Use provided bash scripts (bin/charlie-csl.sh, skills/qwen-local/agent-fallback.sh, skills/qwen-local/fallback-runner.sh) for logging and agent/model operations.

3. Logging and system tracking:

   • Add system log events using /Charlie CSL slash command or by running bin/charlie-csl.sh.
   • Review and update docs/CHARLIE_SYSTEM_LOGS.md for operational changes.

4. Agent memory and configuration:

   • Update daily logs and curated memory in memory/ and MEMORY.md.
   • Keep environment-specific details in TOOLS.md.

5. Model integration:

   • Local LLM calls are handled via Ollama qwen3.5b as defined in openclaw.json and skills/qwen-local/SKILL.md.

Notes

• All operational skills and configurations are local and focused on workspace-specific needs.
• Ensure scripts have appropriate permissions for logging and file operations.
• Memory files should be protected and loaded only in direct sessions.
• Pipeline steps and logs are designed to keep project history clear and enable efficient team collaboration.
• Update agent soul and identity files mindfully and promptly notify users when changes are made.
• For external access or control UI, allowed origins are set in openclaw.json.
• Always respect boundaries and privacy as outlined in SOUL.md and USER.md.