Documentation
¶
Overview ¶
Package bots exposes the productised bot recipes shipped with iterion (the named team — Featurly, Billy, Willy, …) as an embed.FS so the binary can run them by basename from any working directory.
Lookup order at launch time (see pkg/server.resolveWorkflowPath):
- resolve the requested path against the server WorkDir;
- on miss, if the path is a bare basename matching an embedded recipe, materialise the embedded content into the run store and use that path.
Only the curated single-file bot recipes are embedded. Companion .md design journals and large non-recipe assets are intentionally excluded to keep the binary slim. Bundle directories (`<name>/main.bot` + manifest + skills + prompts + attachments) are NOT embedded either — they have to be loaded by explicit path (`iterion run bots/<name>/` or against the packed `<name>.botz`); embedding them would lose the adjacent skills/prompts/attachments resources that make a bundle a bundle, plus encoding the whole tree as embedded bytes inflates the binary far more than a single .bot does.
Index ¶
Constants ¶
This section is empty.
Variables ¶
var Files embed.FS
The three productised bots (feature_dev, whole_improve_loop, branch_improve_loop) each ship as a single-file bundle: only `<name>/main.bot` is embedded — their manifest.yaml + README.md are stripped to keep the binary slim. Larger bundles (whats-next, docs-refresh, sec-audit-*, secured-renovacy, review-pr) carry skills/prompts/attachments alongside main.bot and are deliberately NOT embedded; they have to be loaded by explicit path (`iterion run bots/<name>/` or against the packed `.botz`).
Functions ¶
Types ¶
This section is empty.