doc: add script namespaces section to ARCHITECTURE.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
ab0b354132
commit
d36e75a0a2
|
|
@ -82,6 +82,18 @@ steps=[{parallel:[...]}, {code:"sort"}] — fan-out then transform
|
|||
|
||||
`OLLIE_TOOLS_PATH` defaults to `~/.config/ollie/tools`. `{tool}` steps resolve scripts from this path.
|
||||
|
||||
## Script Namespaces
|
||||
|
||||
User-facing scripts are organized by the 9P namespace they are hosted under and installed to `~/.config/ollie/scripts/{ns}/`:
|
||||
|
||||
| Namespace | Purpose | Scripts |
|
||||
|---|---|---|
|
||||
| `s/` | Session management | `sh`, `ls`, `kill` |
|
||||
| `b/` | Batch job submission and execution | `job`, `q`, `sched` |
|
||||
| `u/` | Utility scripts; compositions of `b/` primitives | `optimize` |
|
||||
|
||||
`b/job` is the core batch runner. `b/q` and `b/sched` are thin wrappers that add foreground-wait and background-submit semantics respectively. `u/` scripts have no special server backing — they are executable scripts that compose other namespaces via the filesystem.
|
||||
|
||||
## Tool Scripts
|
||||
|
||||
All capabilities beyond `execute_code` itself are implemented as tool scripts in `OLLIE_TOOLS_PATH`, invoked via `{tool}` steps. The agent discovers available scripts via `t/idx`.
|
||||
|
|
|
|||
Loading…
Reference in New Issue