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

fix: update remaining active worker wording

Browse Source
This commit is contained in:
Hare
2026-06-26 01:06:20 +09:00
parent da96d06f25
commit cb0c52e787
9 changed files with 21 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/design/compaction.md
+1 -1
View File
@@ -1,6 +1,6 @@
# Compaction
Compaction exists because long-running Pods need durable continuity without sending the entire transcript forever.
Compaction exists because long-running Workers need durable continuity without sending the entire transcript forever.
## Pruning vs compaction
docs/design/memory-knowledge.md
+1 -1
View File
@@ -6,7 +6,7 @@ The authoritative record for work is still code, git history, work item files, t
## Record types
- `summary.md` is resident background context for normal Pods.
- `summary.md` is resident background context for normal Workers.
- `decisions/` stores durable decisions that are useful across turns.
- `requests/` stores durable user requests and preferences.
- `.yoi/knowledge/` stores curated Knowledge records when available.
docs/design/plugin-packages.md
+1 -1
View File
@@ -99,7 +99,7 @@ Collision handling:
Discovery is a read-only inventory operation. It may report package metadata, validation errors, source, canonical store path, and deterministic digest. It must not initialize any runtime contribution.
Enablement is a resolved runtime plan. It should come from Profile/manifest configuration or another explicit local policy layer, then be recorded into the resolved Manifest/session metadata used to start the Worker. Restored Pods should use that resolved enabled-plugin plan instead of silently re-running fresh discovery and picking newer packages. Fresh discovery must not silently upgrade a restored Worker.
Enablement is a resolved runtime plan. It should come from Profile/manifest configuration or another explicit local policy layer, then be recorded into the resolved Manifest/session metadata used to start the Worker. Restored Workers should use that resolved enabled-plugin plan instead of silently re-running fresh discovery and picking newer packages. Fresh discovery must not silently upgrade a restored Worker.
A minimal implemented enablement record is shaped like this. `version` is an exact package-version requirement; richer range constraints are deferred. `digest` is optional in authoring config, but fresh startup records the resolved digest into runtime metadata.
docs/design/tool-permissions-scope.md
+1 -1
View File
@@ -22,7 +22,7 @@ Directory traversal tools should not follow symlink directories as a way around
## Delegation
Child Pods receive an explicit subset of the parent's scope. Delegation is a capability loan, not a copy of all parent authority.
Child Workers receive an explicit subset of the parent's scope. Delegation is a capability loan, not a copy of all parent authority.
When a child stops, shuts down, or is pruned as unreachable, delegated write permissions must be reclaimed. Explicit base denies remain in force.