alivebundle

# Bundle Manage the bundle lifecycle: create, share, graduate, status. Bundles are the unit of focused work — anything with a deliverable or a future audience. This skill is invoked by the bundle awareness injection, by the load skill's "what are you working on?" prompt, or directly by the human via `/alive:bundle`. --- ## Detection — When to Invoke The spectrum: | | One-off | Bundle | Walnut | |---|---------|--------|--------| | Sessions | This session only | Likely >1, or worth returning to | Own ongoing lifecycle | | Deliverable | No | Yes — ship, send, or reference later | Multiple deliverables | | Audience | Just you, right now | Someone specific, or future-you | Has its own people | **Trigger:** "Does this have a deliverable or a future audience?" If yes -> bundle. --- ## Bundle Types ### Outcome Bundle The default. A body of work with a deliverable — a document, a plan, a shipped feature. Has drafts, versions, a finish line. ### Evergreen Bundle Living reference material that grows over time. No "done" state — it accumulates. Research collections, style guides, knowledge bases. Status cycles between `active` and `maintaining` rather than progressing to `done`. --- ## Bundle Location Bundles live flat in the walnut root. A folder is a bundle if it contains `context.manifest.yaml`. ``` nova-station/ # walnut root _kernel/ shielding-review/ # bundle context.manifest.yaml raw/ launch-checklist/ # anothe...