yoi/crates/manifest
2026-06-26 00:05:57 +09:00
..
src refactor: rename pod crate to worker 2026-06-26 00:05:57 +09:00
Cargo.toml refactor: rename llm worker crate to engine 2026-06-25 22:46:26 +09:00
README.md refactor: rename pod crate to worker 2026-06-26 00:05:57 +09:00

manifest

Role

manifest resolves reusable profile/configuration inputs into the concrete runtime Manifest used to create or restore Pods.

Boundaries

Owns:

  • Profile and Manifest data structures
  • source/partial/resolved configuration layering
  • path and prompt-resource resolution
  • tool permission and filesystem scope configuration types
  • model/provider references as configuration records

Does not own:

  • provider HTTP clients or secret lookup implementation (provider, secrets)
  • Worker lifecycle (worker)
  • product CLI parsing (yoi)
  • generated memory records (memory)

Design notes

Profiles are reusable recipes; resolved Manifests are runtime contracts. Keep runtime-bound fields such as Worker name, concrete delegated scope, sockets, session pointers, and raw secrets out of reusable Profiles.

See also