Layered Soul integration
Layered Soul integration
← index
clawdie/layered-soul is theportable, harness-agnostic source of durable identity + reviewed context. This doc
records how Colibri consumes it today, and what is still planned — so the
contract isn't mistaken for fully-built.
What's wired (works now)
Reviewed skills import into Colibri's existing skills catalog:
scripts/import-layered-soul.sh
It reads each skills SKILL.md file (frontmatter name / description; category
soul) and INSERT OR IGNOREs a row into the skills table. references/ and
templates/ under a skill are supporting material, not separate skills. Same
table as clawdie-iso/scripts/import-clawdie-skills.sh; idempotent, safe to re-run.
What's deferred (planned, not built)
The the Colibri adapter in layered-soul names a "Layered Memory Fabric" with
three stores — system_skills, system_brain, system_ops. As of 2026-06-13
only a single flat skills table exists; the rest is design only
(docs/COLIBRI-SKILLS-PLAN.md), so the importer intentionally does not target it.
| Layered Soul source | Target (planned) | Status |
|---|---|---|
| skills SKILL.md files | system_skills | imported into the flat skills table today |
| memories/curated markdown files | system_brain | NOT imported — no store yet (the importer reports a count) |
| converted task/job manifests | system_ops | NOT implemented |
Direction (one-way)
layered-soul (git) is the source of truth; Colibri is a consumer.
Import flows one way (repo → Colibri). Always curate skills in the source repo,
then re-import — runtime copies are ephemeral consumers.
Closing the gap (future work)
1. Implement system_brain per COLIBRI-SKILLS-PLAN.md, then extend the importer
to load curated memories.
2. Migrate the flat skills table to the planned system_skills schema.
3. Define and import system_ops task/job manifests.
See also
- skills-catalog — Colibri's read-only runtime skill consumer
- store-schema — planned
system_skills/system_braintables