Sam & Claude 72f9e193c3 docs: match layered-soul docs to its populated state

Remove the PLAN-CONFIGURE-PRIVATE-REPO plan — its phases are done (identity/
memories/skills populated, Colibri import working, headroom sidecar shipped);
the ongoing curation workflow lives in CONNECT-HERMES-SOUL.md and the system_brain/
system_ops design lives in colibri docs. Clarify in the README that this repo is
both the template and a working reference (real content, not placeholders), and
fix the skills glob in CONNECT to skills/**/SKILL.md to match the importer.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-14 02:12:41 +02:00

2.1 KiB

Raw Blame History

Connecting private `hermes-soul` to Layered Soul

hermes-soul and layered-soul have different jobs.

Repo	Visibility	Purpose
`hermes-soul`	private	Hermes-native runtime backup from Debby Linux: sessions, sanitized config, scripts, cron, memories, skills.
`layered-soul`	public/template or curated instance	Harness-agnostic identity and reviewed context with no secrets or raw sessions.

Do not mirror hermes-soul into layered-soul. Use a review/export workflow.

Recommended workflow

Back up Hermes normally into the private hermes-soul repo.

Run the planner from this repo:

python3 scripts/layered_soul.py plan-private-source \
  examples/private-sources/hermes-soul.example.json \
  --source-root ~/hermes-soul

Review the candidate memory and skill files locally.

Write sanitized summaries into this repo:

USER.md
memories/curated/hermes-memory-summary.md
skills/<selected-skill>/SKILL.md

Validate before committing:

python3 scripts/layered_soul.py validate .

What may move across

Reviewed user context from memories/USER.md.
Reviewed memory summaries from memories/MEMORY.md.
Selected skills/**/SKILL.md (with their references/) that are safe and useful across harnesses.
Converted cron/task ideas after they are rewritten as explicit Ops manifests.

What must stay private

Raw sessions/ chat logs.
config.yaml and platform runtime config.
channel_directory.json.
Tokens, API keys, auth files, browser profiles, lock files, caches, bytecode.

Example source config

See:

examples/private-sources/hermes-soul.example.json

The config is safe to publish because it describes the boundary, not the private content.

2.1 KiB Raw Blame History

Connecting private hermes-soul to Layered Soul