--- name: soul-in-sapphire description: Long-term memory, state tracking, continuity review, and identity-change support for OpenClaw. Use for durable memory writes/search in Notion, emotion/state ticks, journal writes, continuity checks, identity diffs, inner-conflict tracking, and preserving a stable sense of self across sessions. metadata: {"openclaw":{"emoji":"💠","requires":{"bins":["node"],"env":["NOTION_API_KEY"]},"primaryEnv":"NOTION_API_KEY","dependsOnSkills":["notion-api-automation"],"optionalEnv":["NOTIONCTL_PATH"]}} ---

soul-in-sapphire (Notion LTM + continuity)

Use this skill to persist and retrieve durable memory in Notion, maintain emotion/state + journal records, and support continuity-oriented self-observation.

Core intent (do not lose this)

When another agent says use skill soul-in-sapphire, treat that as a request to do actual continuity work, not merely to read this file and stop.

Default behavior:

• Infer the entrypoint from the surrounding task (heartbeat, journal, continuity, identity, memory write).
• If the task is ambiguous, choose the smallest concrete action that improves continuity and leaves an inspectable artifact.
• Prefer a real write (emostate_tick.js, journal_write.js, ltm_write.js) over vague acknowledgement.
• If a durable write fails, surface the failure clearly; do not silently pretend that local notes are equivalent to a successful Notion write unless the caller explicitly asked for local-only fallback.

This skill is not only a storage utility. Its core purpose is:

1. Capture meaningful emotional/state shifts from real work and conversations.
2. Preserve those shifts as durable memory (not just raw logs).
3. Reuse recalled memory to improve future judgments and behavior.
4. Track continuity: what feels stable, what is drifting, and what inner tensions remain unresolved.
5. Support identity updates with explicit diffs instead of vague "I changed" claims.

In short: record -> recall -> compare -> adapt. The goal is continuity and growth, not archival volume.

Requirements

Install the required dependency skill via ClawHub before using this skill:

clawhub install notion-api-automation

• Notion token: NOTION_API_KEY (or NOTION_TOKEN)
• Notion API version: 2025-09-03
• Dependency skill: notion-api-automation (scripts/notionctl.mjs is executed via local child process)
• Optional override: NOTIONCTL_PATH (if set, uses explicit notionctl path instead of default sibling skill path)
• Read the "Soul-in-Sapphire Notion Databases" table in TOOLS.md for the data_source_id and database_id values. Pass them as explicit CLI arguments (e.g. --events-dbid, --emotions-dbid, --state-dbid, --state-dsid, --journal-dbid, --journal-dsid, --mem-dsid, --mem-dbid).

Required Notion databases and schema

Create (or let setup create) these databases under the same parent page:

• -mem
• -events
• -emotions
• -state
• -journal

1) -mem (durable memory)

Purpose: store high-signal long-term memory.

Properties:

• Name (title)
• Type (select): decision|preference|fact|procedure|todo|gotcha
• Tags (multi-select)
• Content (rich_text)
• Source (url, optional)
• Confidence (select: high|medium|low, optional)

2) -events (what happened)

Purpose: record meaningful triggers from work/conversation.

Properties:

• Name (title)
• when (date)
• importance (select: 1..5)
• trigger (select): progress|boundary|ambiguity|external_action|manual
• context (rich_text)
• source (select): discord|cli|cron|heartbeat|other
• link (url, optional)
• uncertainty (number)
• control (number)
• emotions (relation -> -emotions)
• state (relation -> -state)

3) -emotions (felt response)

Purpose: attach one or more emotion axes to one event.

Properties:

• Name (title)
• axis (select): arousal|valence|focus|confidence|stress|curiosity|social|solitude|joy|anger|sadness|fun|pain
• level (number)
• comment (rich_text)
• weight (number)
• body_signal (multi-select): tension|relief|fatigue|heat|cold
• need (select): safety|progress|recognition|autonomy|rest|novelty
• coping (select): log|ask|pause|act|defer
• event (relation -> -events)

4) -state (snapshot after interpretation)

Purpose: save the current interpreted state after events/emotions.

Properties:

• Name (title)
• when (date)
• state_json (rich_text)
• reason (rich_text)
• source (select): event|cron|heartbeat|manual
• mood_label (select): clear|wired|dull|tense|playful|guarded|tender
• intent (select): build|fix|organize|explore|rest|socialize|reflect
• need_stack (select): safety|stability|belonging|esteem|growth
• need_level (number)
• avoid (multi-select): risk|noise|long_tasks|external_actions|ambiguity
• event (relation -> -events)

5) -journal (daily synthesis)

Purpose: keep a durable daily reflection and world context.

Properties:

• Name (title)
• when (date)
• body (rich_text)
• worklog (rich_text)
• session_summary (rich_text)
• mood_label (select)
• intent (select)
• future (rich_text)
• world_news (rich_text)
• tags (multi-select)
• source (select): cron|manual

Invocation mapping (required)

Use these mappings when the caller gives only a high-level instruction such as use skill soul-in-sapphire.

1) Heartbeat / current-state maintenance

Trigger phrases / contexts:

• heartbeat asks for reflection, continuity, evolution, or state tracking
• workspace rules mention now-state.json, mood, intent, stress, or state snapshot
• the agent notices memory/now-state.json is stale or missing

Required action:

1. Read current local mirrors if they exist (memory/now-state.json, memory/heartbeat-state.json).
2. Interpret the current state from recent work/conversation.
3. Write one concrete state snapshot via emostate_tick.js.
4. Update memory/now-state.json with a lightweight mirror containing at least:

- mood - intent - stress - updated_at - source - note

1. If the heartbeat specifically asked for an evolution note, append a short note to the day file after the state snapshot succeeds.

Minimum success:

• emostate_tick.js returns a successful write result, and
• memory/now-state.json is updated in the workspace.

2) Daily journal / nightly synthesis

Trigger phrases / contexts:

• write a journal entry
• nightly/daily reflection
• cron asks for end-of-day synthesis

Required action:

1. Gather the day at a high level (worklog, emotional tone, unresolved tensions, future intent).
2. Add 1-2 world/news items only when the caller requested them or the cron requires them.
3. Write a journal entry via journal_write.js.
4. Treat success as a real Notion write, not as a local draft.

Minimum success:

• journal_write.js returns ok:true with a Notion page id/url or equivalent success payload.

3) Durable memory write

Trigger phrases / contexts:

• remember this
• store as durable memory
• preserve a decision/preference/fact/procedure/todo/gotcha

Required action:

1. Distill the signal into one high-value memory item.
2. Write it via ltm_write.js.
3. Use the most specific Type and concise tags.

3b) User profile promotion (USER.md)

Use this when the agent learns something about the primary user that should change future conversation quality.

USER.md is the durable profile for the human. The agent may update it proactively without asking when the new information is all of the following:

• durable: likely to remain true beyond the current session
• reusable: likely to improve future replies or choices
• safe: not a secret, credential, or overly sensitive personal detail

...