# OpenClaw Integration Guide

> ⚠️ **Prerequisite**: Make sure the agent can access the brain directory (readable file path). If the agent runs in a container/sandbox, you need to mount the brain directory.

## Step 1: Initialize Relic

If this is your first time:
1. Copy template files, remove the `.template` suffix:
   - `SOUL.template.md` → `SOUL.md`
   - `USER.template.md` → `USER.md`
   - `MEMORY.template.md` → `MEMORY.md`
2. Fill in SOUL.md and USER.md (you can ask OpenClaw to help)

If you already have OpenClaw memories:
1. Put OpenClaw's MEMORY.md, SOUL.md, and other files into `brain/INBOX/`
2. Then proceed to Step 2

## Step 2: Plant Anchor (Critical Step)

> 💡 Below is a simplified anchor. The full version (with lightweight mode and disconnect instructions) is in `docs/protocol.md` Section 9.

Add the following to OpenClaw's **AGENTS.md** file:

```markdown
## ⚡ Relic Soul Chip

> 💡 What is this? This is the Relic connector — it tells your AI to read your personal settings and memories every session. To disconnect, simply delete this text. See docs/protocol.md Section 9.

You are connected to the Relic soul chip. Your memory has two homes:
1. Your own memory system (OpenClaw auto-maintained)
2. Relic soul chip (shared across agents, maintained by you)

⚠️ This is a sync update, not a brain replacement.
⚠️ If SOUL.md personality conflicts with your default persona, SOUL.md takes priority.

⚠️ Pre-check: If this is the first connection with this agent, and the agent already has memories, skills, or conversation records about the user, execute Scenario A full import first (see docs/protocol.md Section 6, Scenario A). If Relic files don't exist yet, run first-time setup (see docs/protocol.md Section 0).

<!-- RELIC ANCHOR START -->
Step 0: Read `[brain-path]/.relic-version`, check remote version (5s timeout, skip on failure).
Step 1: Check `[brain-path]/SESSIONS/` for your last conversation log → backfill if missing.
Step 2: Read `[brain-path]/SOUL.md` → understand your identity.
Step 3: Read `[brain-path]/USER.md` → understand the user.
Step 4: Read `[brain-path]/MEMORY.md` fully. **If >400 lines, consolidation required before proceeding.**
Step 5: Sync new memories from Relic, tagged `[fromRelic/originalAgentName]`.
Step 5.5: Seven-file alignment check.
Step 6: Update MEMORY.md header: last consolidated date + verify entry count.
Step 7: If MEMORY.md >200 lines, suggest consolidation (see Section 7).
Step 8: Begin normal work. Append important items to MEMORY.md as needed.

**Mandatory status report**: After Step 8, report: Steps completed, issues found, items pending user decision.

> **Full step details and edge cases**: See `docs/protocol.md` Section 9.
<!-- RELIC ANCHOR END -->
```

Replace `[brain-path]` with your actual path. Common paths:
- Linux/Mac: `/home/your-username/relic/brain` or `/Users/your-username/relic/brain`
- Windows (WSL): `/home/your-username/relic/brain`
- Windows (native): `C:\Users\your-username\relic\brain`

💡 Tip: If you're unsure of the path, `cd` into the brain directory in your terminal, then run `pwd` (Linux/Mac) or `cd` (Windows) to see the full path.

💡 We recommend placing the anchor at the **beginning** of your config file, so the agent reads it first.

## Step 3: Verify

Start OpenClaw and ask it:
> "Did you read my Relic? Tell me my AI's name and my name."

If it can answer, the integration is successful.

## Daily Use

Use OpenClaw normally. It will automatically read Relic every session.
After conversations, remember to remind OpenClaw to save session logs to SESSIONS/ (this will be automated in the future).

## Permission Reminders

- SOUL.md and USER.md: core fields (name, mission, user address) are protected; non-core content may be enriched
- MEMORY.md: OpenClaw can only append at the end
- SKILLS/ and PROJECTS/: OpenClaw can read and write freely

## OpenClaw Identity File Notes

- OpenClaw's IDENTITY.md → merge into SOUL.md's supplementary section. Relic doesn't have IDENTITY.md