// concepts · 07
Repository map and runtime layout
Okami has two layouts: the Python package (okami/) and the runtime state created when agents run. This split keeps versioned code separate from live sessions, memor…
Project root
| path | role |
|---|---|
| okami/ | main package: CLI, harness, providers, channels, memory, skills and integrations |
| tests/ | pytest suite for harness, gateway, sandbox, memory, providers, TUI, API and policy |
| skills/ | bundled SKILL.md workflows, scanned before use |
| examples/company/ | multi-agent company example: cto, ui and backend |
| deploy/ | Dockerfile and docker-compose |
| scripts/ | one-command installers |
| docs/ | architecture, production, structure, roadmap and competitive research |
| okami.yaml / okami.policy.yaml | base config and authored conformance posture |
Package domains
core/ harness · tools · approval · sandbox · safe_io
llm/ providers · transports · oauth · retry · imagegen
gateway/ endpoint · sessions · checkpoints · approvals · groups
channels/ terminal · telegram · slack · discord · mattermost · paperclip
memory/ sqlite_fts5 · holographic · honcho · layered · compaction
learning/ auto-skill · persona · taste · tuning
integrations/ mcp · acp · browser · referencesAgent runtime
agents/<id>/
agent.yaml
SOUL.md · VOICE.md · PERSONA.md
.okami/
sessions/<chat>.jsonl
memory.db · taste.json · persona_signals.json
checkpoints/journal.jsonl
audit.jsonl · events.jsonl · tool_outputs/