sanctuary-orchestrator-integration
Sanctuary Orchestrator Integration
Status: Active
Domain: Project Sanctuary
Depends on: agent-loops/orchestrator
Purpose
This skill is the Sanctuary-specific glue layer that bridges the Guardian ecosystem (guardian-onboarding) to the generic agent-loops/orchestrator.
Project Sanctuary operates under a strict Separation of Concerns (Protocol 128). To prevent architectural drift, the Orchestrator executes cognitive patterns, but ONLY the Guardian is authorized to serialize state or modify external systems.
Separation of Concerns Matrix
| Responsibility | Owner | Execution Path |
|---|---|---|
| Protocol Alignment | Guardian | cortex_guardian_wakeup (Bootloader) |
| Feature Formulation | Guardian | spec-kitty.specify → spec-kitty.tasks |
| Loop Routing | Orchestrator | agent_orchestrator.py |
More from richfrem/project_sanctuary
excel-to-csv
>
1sanctuary-memory
Project Sanctuary-specific memory configuration. Maps the generic memory-management tiered system to Sanctuary's actual file paths, storage backends (RLM, Vector DB, Obsidian, HuggingFace), and persistence workflows.
1sanctuary-spec-kitty
Project Sanctuary-specific skill for Spec-Driven Development. Knows the project's constitution, safety rules, AUGMENTED.md best practices, and how the spec-kitty-plugin should be configured for this project.
1sanctuary-soul-persistence
Project Sanctuary-specific skill for managing Soul persistence to HuggingFace. Knows the exact .env parameters, discovery tags, dataset structure, and persistence workflows for this project. Uses the generic huggingface-utils plugin.
1sanctuary-obsidian-integration
Project Sanctuary-specific skill for managing the Obsidian vault as an external hippocampus. Knows the vault path, naming conventions, and integration patterns. Uses the generic obsidian-integration plugin.
1