Hatchlings need access to curated reference materials without duplicating files into each workspace.
Pattern: The Librarian
- Shared read-only volume mount per client/domain
- Operator (Zephyr) curates and updates the collection
- Hatchlings mount it as read-only reference material
Implementation:
- Convention:
/share/Container/shared-resources/<client>/ on NAS
hatch.sh --library <path> adds a read-only volume mount to docker-compose.yml
- Hatchling workspace gets a
reference/ symlink or AGENTS.md instruction pointing to /library/
fleet.sh shows library mounts in status output
Example docker-compose addition:
volumes:
- ./data:/home/openclaw/.openclaw:rw
- /share/Container/shared-resources/chc:/home/openclaw/library:ro
This solves the Todd/CHC problem: we have research and reference materials that his bot needs but should not own or modify.
Implementation notes: no separate validation report docs in PR, keep docs minimal.
Hatchlings need access to curated reference materials without duplicating files into each workspace.
Pattern: The Librarian
Implementation:
/share/Container/shared-resources/<client>/on NAShatch.sh --library <path>adds a read-only volume mount to docker-compose.ymlreference/symlink or AGENTS.md instruction pointing to/library/fleet.shshows library mounts in status outputExample docker-compose addition:
This solves the Todd/CHC problem: we have research and reference materials that his bot needs but should not own or modify.
Implementation notes: no separate validation report docs in PR, keep docs minimal.