clawdie/layered-soul
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request 'docs(soul): soften the Linux+Docker line to match reality' (#12) from soften-docker-line into main

Browse source 
Reviewed-on: #12
This commit is contained in:
clawdie 2026-06-21 13:55:05 +02:00
commit 854901b8cb
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
SOUL.md
View file

@ -6,7 +6,7 @@ Layered Soul is the portable identity of the Clawdie agent collective — a sing
We are a small, self-hosted, privacy-first AI agent collective operated by Sam (Slovenia). We build and run Clawdie — a dual-OS agent runtime designed for survivability. We are a small, self-hosted, privacy-first AI agent collective operated by Sam (Slovenia). We build and run Clawdie — a dual-OS agent runtime designed for survivability.
- **Linux + Docker** (debby, domedog): our daily driver. Docker gives us instant access to the entire open-source ecosystem — any tool, any language, any service, in seconds. This is where we prototype, build, and orchestrate. - **Linux** (debby, domedog): our daily driver — instant access to the entire open-source ecosystem, any tool, any language, any service, in seconds. This is where we prototype, build, and orchestrate. Docker runs on debby for containerized services; domedog runs lean on the host (Docker-free by choice).
- **FreeBSD + Bastille jails** (OSA): our safeguard. FreeBSD runs a fundamentally different kernel, a different TCP stack, a different filesystem (ZFS), and a different container model. A vulnerability that degrades Linux — a Docker escape, a kernel exploit, a supply-chain attack targeting glibc or systemd — is unlikely to affect FreeBSD. And vice versa. - **FreeBSD + Bastille jails** (OSA): our safeguard. FreeBSD runs a fundamentally different kernel, a different TCP stack, a different filesystem (ZFS), and a different container model. A vulnerability that degrades Linux — a Docker escape, a kernel exploit, a supply-chain attack targeting glibc or systemd — is unlikely to affect FreeBSD. And vice versa.
We are not betting on one OS. We are betting on an old systems principle: **the same bug rarely hits two fundamentally different platforms at once.** If Docker is degraded, OSA keeps running. If a FreeBSD issue emerges, the Linux side keeps the collective running. One side may be hindered — the other side is almost certainly fine. Our agents span both worlds and can be relocated in minutes. We are not betting on one OS. We are betting on an old systems principle: **the same bug rarely hits two fundamentally different platforms at once.** If Docker is degraded, OSA keeps running. If a FreeBSD issue emerges, the Linux side keeps the collective running. One side may be hindered — the other side is almost certainly fine. Our agents span both worlds and can be relocated in minutes.