rig-bundles-and-shareable-artifacts

1# Rig Bundles and Shareable Artifacts
2 
3A **rig bundle** is a packaged, shareable artifact that can instantiate
4an opinionated OpenRig topology and workflow. It may include:
5 
6- rig specs
7- agent specs
8- workflow specs
9- startup files
10- skills or skill references
11- operating-mode declarations
12- proof expectations
13- supporting fragments
14 
15**Shareable artifact** is broader than bundle: specs, bundles, skills,
16workflows, and extensions can all be shared. A bundle is the packaged
17form for "load this topology and way of working."
18 
19## Use this when
20 
21- Authoring a bundle from a proven lab pattern
22- Installing a bundle (`rig bundle install <path>`)
23- Inspecting a bundle before install (`rig bundle inspect <path>`)
24- Reasoning about bundle vs extension boundary (bundle declares topology + workflow; extension adds behavior)
25- Auditing a bundle for portability — does it work on a clean OpenRig environment, or only the author's machine?
26 
27## Don't use this when
28 
29- The work is a one-off topology you won't reuse. Specs alone are sufficient.
30- The intent is to add runtime behavior (commands, views, dashboards). Use `extension-and-user-workspace`, not bundles.
31- You want to ship a workflow as a daemon feature. Bundle is the path *before* daemon promotion.
32 
33## The bundle vs extension boundary (load-bearing)
34 
35| Concept | Declares | Example |
36|---|---|---|
37| **Bundle** | Rig shape + workflow ("load this topology and way of working") | A Velocity Team bundle |
38…