① myorch/flows/ · profiles/ · tools/

② myorch-knowledge/<project>/project.yaml · prompts/ · guide/ · checks.sh · sources/ · _templates/

Knowledge source contentlocal directory (under ~/orca/kb) or git repository

expanded at start · myorch init installs tools/

project sync (versioned snapshots)

synced automatically when a run starts

④ volume myorch-artifacts · all a sandbox can see

runs/<run>/workspace: code, docs/, .myorch/flow.yaml, each step's artifacts and logs
mounted read-write at /sandbox/workspace

projects/<project>/<version>/project pack snapshot
mounted read-only at workspace/project

knowledge/<name>/<version>/knowledge source snapshot
mounted read-only at workspace/knowledge/<name>

shared/<project>/<name>/caches across runs (build cache, sweep cursor)
mounted read-write only for steps that ask

tools/helper commands
mounted read-only at /sandbox/bin

jobs/<key>/one-off jobs (knowledge source sync etc.)

write back: project-apply commits → new snapshot

worker writes events and live output

push the branch after approval, no PR

② myorch-knowledge/proposals adopted by learn · onboard · postmortem, knowledge sources registered in the console; all git commits

③ myorch-data/temporal.db (ended runs kept 24 hours) · events.db · evals/ · learn/ · ui/ · slack/
the console reads the run list and conversations here

The project's GitHub repositorypushes only this run's branch

At run start, the mandate pins the versions of the project pack and knowledge sources. ①②③ are on the host; sandboxes cannot see them.