docs: reorganize developer documentation

This commit is contained in:
2026-06-01 20:59:32 +09:00
parent e6c458021c
commit 9dcbd4c3e0
83 changed files with 1320 additions and 5649 deletions
+30
View File
@@ -0,0 +1,30 @@
# tools
## Role
`tools` implements built-in tools and shared tool execution helpers used by Pods.
## Boundaries
Owns:
- built-in filesystem, web, memory, and Pod-management tool implementations where applicable
- bounded tool output formatting
- scope-aware file operation helpers
- tool-facing diagnostics suitable for history/model consumption
Does not own:
- manifest permission policy definition (`manifest`)
- Worker tool-loop semantics (`llm-worker`)
- Pod lifecycle decisions (`pod`)
- UI presentation (`tui`)
## Design notes
A tool implementation must assume model input is untrusted. Permission policy, scope checks, output bounding, and redaction are part of the safety boundary, not optional UI behavior.
## See also
- [`../../docs/design/tool-permissions-scope.md`](../../docs/design/tool-permissions-scope.md)
- [`../../docs/design/memory-knowledge.md`](../../docs/design/memory-knowledge.md)