What is a Pack
A Pack is a reusable automation you call like a function. Its definition — input schema, steps, and gates — lives on the server; every run executes locally on your desktop.
Definition
- Id — {author}/{slug}; the bom/ namespace marks Bom’s curated system Packs
- Version + input schema — the JSON Schema rendered as the start form
- Steps — llm, browser, image, gate, and forEach over a list
- Gates — allowed domains and tools, per-cycle budgets, quiet hours, publish caps
Execution model
- You press Run — the server admits the request and delivers a run intent to your desktop.
- The desktop engine executes every step locally, journaling as it goes so a crash resumes instead of restarting.
- Irreversible steps are claimed in an idempotent ledger — a retry can never publish the same thing twice.
- The server mirrors a bounded run summary so your other devices can watch progress.
Safety
- Circuit breaker — a pack that keeps failing is paused before it burns more cycles
- Quality judge — content is reviewed before any irreversible publish step
- Budgets — per-cycle caps on LLM turns, tool calls, and cost