Recommended layout
What each path owns
| Path | Builder responsibility |
|---|---|
agent/system.md | Base purpose, rules, and response expectations |
agent/settings.json | Default model, thinking level, and active tools |
agent/skills/ | Reusable, immutable instruction packages |
agent/prompts/ | Named prompt templates |
agent/extensions/ | Sandbox-hosted JavaScript extensions |
sandbox/workspace/ | Seed files copied only into new run workspaces |
salambo.yaml | Deployment, image, region, egress, environment, secrets, and extension entrypoints |
Build-time and runtime paths
The source path and runtime path are intentionally different:| Source | Hosted behavior | Mutability |
|---|---|---|
agent/system.md | Compiled into the deployment manifest | Immutable per deployment |
agent/skills/ | Projected as agent resources | Read-only |
agent/extensions/ | Loaded by the sandbox extension host | Read-only |
sandbox/workspace/ | Copied to /workspace for a new run | Mutable and checkpointed |
/workspace is builder-owned mutable state. Platform runtime files are not exposed through managed agent file tools.
Files Salambo generates
salambo manifest compiles source files into a deployment manifest containing normalized model settings, instructions, skills, prompts, tool declarations, hook subscriptions, and workspace policy. Do not edit the compiled manifest manually.
What does not belong here
- Salambo, storage, or provider credentials in source files
- Code that expects access to trusted worker memory
- Mutable customer work under the immutable
agent/resource projection