@openrig/cli 0.5.7 → 0.5.8

package/daemon/docs/reference/chain-file-convention.md

@@ -12,7 +12,7 @@ walking from where they stand toward the root, reading the same-named file at
 each level. No pointers to follow, no branching, no per-level names. Inventing
 a level-specific name breaks every walker.
 
-Chain files sit on **nodes** (an instance, a rig, a seat; a mission, a slice)
+Chain files sit on **nodes** (an instance, a rig, a pod, a seat; a mission, a slice)
 — never on shelves (`rigs/`, `seats/`, `missions/` are containment, not
 nodes, and carry no chain file).
 
@@ -20,7 +20,7 @@ nodes, and carry no chain file).
 
 | tree | path shape | carries | ships? |
 |---|---|---|---|
-| **Topology** | instance → rig → seat | how work is done here | **yes** — generally applicable defaults ship in source |
+| **Topology** | instance → rig → pod → seat | how work is done here | **yes** — generally applicable defaults ship in source |
 | **Project** | project → mission → slice | what is being built | **no** — depends on what the user builds; see below |
 
 ### The topology tree
@@ -35,13 +35,15 @@ instance):
 ```
 <topology.root>/<NAME>.md                         # instance altitude
 <topology.root>/rigs/<rig>/<NAME>.md              # rig altitude
+<topology.root>/rigs/<rig>/pods/<pod>/<NAME>.md   # pod altitude
 <topology.root>/rigs/<rig>/seats/<seat>/<NAME>.md # seat altitude
 ```
 
-**The pod level is deliberately skipped** (design decision, March 2026: agent
-specs stay flat under the rig so any agent composes into any rig; pods felt
-too restrictive — revisit someday, not now). Pod-class tactical content ships
-as a rig-altitude file named for its audience (see "craft defaults" below).
+The engine creates the instance root, rig directory, and each declared pod
+directory when it materializes topology, even when no authored chain default
+exists. Pod context remains optional: use that altitude only for knowledge
+shared within one context domain. Cross-pod guidance still belongs at the rig
+altitude.
 
 Established chain names on the topology tree:
 
@@ -78,11 +80,13 @@ no path literal.
 
 ## The trace
 
-`rig context trace --rig <rig> [--seat <seat>] --name <NAME>.md` performs the
-walk: it prints each altitude root-first (general → specific), marks whether
-content came from `topology.root`, the legacy tree (with the advisory on
-stderr), or is absent, and needs no running daemon — orientation is exactly
-when the daemon may be down. `--json` returns the structured result.
+`rig context trace --rig <rig> [--pod <pod>] [--seat <seat>] --name <NAME>.md`
+performs the walk: it prints each selected altitude root-first (general →
+specific), marks whether content came from `topology.root`, the legacy tree
+(with the advisory on stderr), or is absent, and needs no running daemon —
+orientation is exactly when the daemon may be down. Existing rig/seat traces
+remain valid; selecting `--pod` adds that context domain between them. `--json`
+returns the structured result.
 
 Your reads ARE the walk: a trace assembled from memory is a recitation that
 reproduces the drift it was meant to catch. Run it; do not recall it.
@@ -90,7 +94,8 @@ reproduces the drift it was meant to catch. Run it; do not recall it.
 ## Shipped defaults and the curation path
 
 Included rigs (product-team first) ship sensible-default chain files at the
-rig, seat, and instance altitudes, installed under `topology.root` at rig-up.
+applicable instance, rig, pod, and seat altitudes, installed under
+`topology.root` at rig-up.
 A shipped default is a **starting point** the occupying team appends to — it
 is never overwritten by a later rig-up (existing files win).
 

package/daemon/docs/reference/release-boundary.md

@@ -74,12 +74,36 @@ playbook.
 ## 6. The capability-delta lifecycle (standing law)
 
 Each release's capability delta is authored at the fence and bound to the exact
-published cut. Canon absorbs its named items; the canon header then names the delta,
-which EXPIRES it — verify the expiry fired, and never cite an expired delta. The new
-release's delta obligations start at ITS cut. A delta that outlives its absorption
-is a stale teaching site wearing a version number.
+published cut. Its baseline is the canon's actual last-absorbed marker, not an
+assumption that the immediately prior semver was absorbed. When canon is behind, the
+new delta is a cumulative synthesis of every intervening delta, preserving
+supersessions and pivots rather than concatenating old prose.
 
-## 7. What deliberately does NOT happen at the boundary
+Canon absorbs the kept public-product truths; the canon header then names the delta,
+which EXPIRES it — verify the expiry fired, and never cite an expired delta. Private
+project topology, host practice, and release ownership go to the versioned project
+world instead of leaking into the public package. The new release's delta obligations
+start at ITS cut. A delta that outlives its absorption is a stale teaching site
+wearing a version number.
+
+## 7. World absorption and discoverability
+
+- Every changed capability gets one small map: **user situation · current capability
+  · authoritative source · natural first product encounter · durable context home ·
+  clean-agent probe**. Record an already-good route and leave it alone.
+- Prefer point-of-need truth from the existing `--help`, error, command output, live
+  state, context catalog, work install, or skill router. The world install supplies
+  width and ontology; it should not copy exact facts a live surface can derive.
+- The release mission owns this review before its cut when possible, so public
+  world/help changes ship with the capability. This boundary verifies the exact
+  packaged result, repairs any missed absorption as explicit debt, absorbs private
+  project truth, re-primes, and observes whether a clean world-installed agent
+  reaches the capability from its situation without being told its name.
+- A missing route is a release finding. Repair the smallest existing seam or deposit
+  the evidenced gap into the derivable-context mission; do not create a second
+  capability registry, search service, or world store at the boundary.
+
+## 8. What deliberately does NOT happen at the boundary
 
 - No process migration: situational rules expired at the fence. The standing corpus
   is the four checking principles — verify by effect · evidence at source · honest

package/daemon/docs/reference/sdlc-conventions.md

@@ -73,6 +73,12 @@ should almost never see something that doesn't match what was planned — QA cat
 kicks them back. When the human looks, they map intent → plan → delivered at a glance, mostly by
 scanning screenshots down a single column, and give the final 1% approval.
 
+For a release mission, `mission.yaml` also names the Git strategy before build
+work starts: the branch/ref that is cumulative integration truth, its base, and
+when that truth is reconciled to main. Continuous integration to main and a
+release-line fold followed by one explicit merge are both valid; leaving the
+choice implicit is not.
+
 **The heavier flow — proof contracts, plan-lock, C1 drops, proof-lock — is PART B and is not in
 force unless assigned.**