Dudu-0223
f9f475cbea
Correct the filesystem-wiring claims flagged by codex: no default/example config wires the fs tools yet (the demo agents do file ops through bash), so the docs and RFC no longer assert that "the default product config loads dsh-file-context". They now state the intended stance — a deployment that loads the fs tools is expected to also load dsh-file-context for read-before-write/edit.
13 lines
1.4 KiB
Markdown
13 lines
1.4 KiB
Markdown
# fs/ - filesystem capability family
|
|
|
|
The filesystem stack: a provider seam (text IO + atomic mutation with an optional version guard), a local implementation, a policy gate plugin (observed-state + read-before-edit + version-guarded write/edit), and the model-facing file tools + executor. All **product** packages.
|
|
|
|
| Package | Role | ctx key |
|
|
|---|---|---|
|
|
| `fs/` | Provider seam: text IO + atomic mutation primitives (optional version guard); owns the `fs/*` policy events | `ctx.fs` |
|
|
| `fs-local/` | Local-filesystem `FileSystem` implementation | (registers `ctx.fs`) |
|
|
| `file-context/` | Policy gate plugin: observed-state + read-before-edit + version-guarded write/edit, via the `fs/*` event gate | (no service — `fs/*` listeners) |
|
|
| `tool-fs/` | Model-facing `read`/`write`/`edit` tools AND the executor (reads via `ctx.fs`, owns read windowing, dispatches `fs/*`) | (registers on `ctx.tools`) |
|
|
|
|
The interface lives at `fs/fs/`. A sandboxed, remote, or project-scoped filesystem backend can replace `fs-local` without touching the seam, the policy gate, or the model-facing tool schemas. The policy (`file-context/`) is a plugin that participates only through the `fs/*` event gate, not a service the tool injects — so dropping it gracefully loses the policy and leaves the unconstrained bare provider rather than breaking the tool. A deployment that loads `tool-fs/` is expected to also load it.
|