Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity
c04b1ca289
yoi/crates/pod
History
Hare c04b1ca289
fix: validate spawn delegation authority
2026-06-12 17:10:59 +09:00
..
examples rename: adopt yoi identity 2026-06-01 18:49:23 +09:00
src fix: validate spawn delegation authority 2026-06-12 17:10:59 +09:00
tests fix: separate workspace root from cwd 2026-06-12 01:03:33 +09:00
build.rs cargo fmt 2026-04-27 22:51:07 +09:00
Cargo.toml feat: add built-in ticket tools 2026-06-05 14:52:39 +09:00
README.md docs: reorganize developer documentation 2026-06-01 20:59:32 +09:00

README.md

pod

Role

pod turns an llm-worker Worker into a named runtime entity with manifest configuration, scoped tools, session persistence, protocol handling, and Pod metadata integration.

Boundaries

Owns:

  • Pod lifecycle and socket protocol serving
  • Worker construction around a resolved Manifest
  • session-store and pod-store coordination
  • built-in tool registration under scope/policy
  • spawned-child orchestration hooks

Does not own:

  • provider-specific wire formats (provider / llm-worker clients)
  • product CLI parsing (yoi)
  • TUI display authority (tui)
  • current-state storage schema outside Pod metadata (pod-store)

Design notes

A Pod is runtime authority, not UI state. It should commit model-visible events through history/session paths and keep current Pod-name state in Pod metadata rather than in transient runtime files.

See also