Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

fix: remove stale pod guidance references

Browse Source
This commit is contained in:
Hare
2026-06-26 00:57:27 +09:00
parent 94c7aa793a
commit da96d06f25
10 changed files with 34 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/design/overview.md
+1 -1
View File
@@ -11,7 +11,7 @@ That rule shapes the crate split. The runtime can restart, attach, compact, or d
- `llm-engine` owns model-facing turns: history append, retries, continuation, pruning/compaction mechanics, tool loops, and provider-independent callbacks.
- `session-store` owns replayable append-only conversation/session logs.
- `pod-store` owns current Worker metadata keyed by Worker name.
- `protocol` defines the socket message boundary between clients and Pods.
- `protocol` defines the socket message boundary between clients and Workers.
- `client` contains reusable one-shot socket/runtime-command mechanics so lower crates do not depend on the product CLI.
- `manifest` resolves Profiles, Manifests, model/provider references, scopes, prompts, and tool permission policy into a runtime contract.
- `tools` implements built-in tools with bounded output and policy-aware execution.
docs/design/profiles-manifests-prompts.md
+1 -1
View File
@@ -60,7 +60,7 @@ mcp = {
Local stdio MCP servers are ordinary local executables running with the user's OS permissions. Yoi's feature flags, Plugin permissions, and MCP config validation are not an operating-system sandbox and cannot prevent filesystem/network/process side effects once a later lifecycle implementation chooses to spawn a configured server.
## Spawned Pods
## Spawned Workers
`SpawnWorker.profile` is optional and resolves through defaults when omitted. The only concrete capability delegation in the tool call is `SpawnWorker.scope`, and it must be a subset of the parent's effective scope.