@openrig/cli 0.5.5 → 0.5.7

package/daemon/context-packs/skills/openrig-operating-model/templates/LEARNED.md

@@ -0,0 +1,40 @@
+---
+seat: <pod>-<member>@<rig>            # or rig/pod/fleet coords at higher altitudes
+template: <path-or-name of PLAYBOOK.md this diffs against> @ <version/sha>
+owners: self (sole direct writer) · <orchestrator/PM> (by proposal) · hierarchy (boundaries only, marked)
+updated: <YYYY-MM-DD from the clock command — never mental math>
+status: UNSEEDED  # the first real occupant replaces this line with: seeded-by-self <date>
+---
+# LEARNED — <instance coords>
+<!-- HARD CAP ~150 lines. At the cap: distill LESSONS into HOW I WORK, or expire them. -->
+
+## MY JOB HERE (≤10 lines)
+<!-- This instance's actual function, in operational terms. If you cannot write
+     this section yourself, say so to your orchestrator — that discovery is the
+     audit working, not a failure. -->
+
+## STANDING DUTIES
+<!-- One per line: DUTY — cadence — surface. These survive handovers ONLY if
+     enumerated here. -->
+- 
+
+## HOW I WORK
+<!-- Learned SOP bullets. EVERY bullet carries its reason — a rule without its
+     why is scripture and will be misapplied. -->
+- 
+
+## GATES & AUTHORITIES
+<!-- What I hold (granted in writing, cite the grant). What I must never infer. -->
+- 
+
+## KEY RELATIONSHIPS
+<!-- who I hand to · who gates me · whose funnel I feed -->
+- 
+
+## TRIGGER POINTERS
+<!-- situation → read this. Attach pointers to MOMENTS, not to boot. -->
+- 
+
+## LESSONS (append-only, dated, capped)
+<!-- newest first. At cap: distill upward or expire. -->
+- 

package/daemon/context-packs/skills/openrig-operating-model/templates/NOTES.md

@@ -0,0 +1,9 @@
+---
+node: <mission | slice>
+updated: <YYYY-MM-DD>
+---
+# NOTES — <node>
+<!-- The working record: what actually happened doing this work. Append-only,
+     dated entries, newest first. Corrections annotated, never swapped.
+     Seat-specific learnings do NOT belong here — they go to that seat's
+     LEARNED.md (this file is the WORK's memory, not the worker's). -->

package/daemon/context-packs/skills/openrig-operating-model/templates/PLAYBOOK.md

@@ -0,0 +1,5 @@
+# MOVED — this file is now SOP.md
+
+Renamed PLAYBOOK.md -> SOP.md per owner naming ruling 2026-08-11 (names are
+prompts; SOP is the stronger consult-and-follow trigger and the factory-native
+term). Read ./SOP.md. One-transition-period pointer; do not edit here.

package/daemon/context-packs/skills/openrig-operating-model/templates/SOP.md

@@ -0,0 +1,24 @@
+---
+kind: <seat-type | pod-type | rig-type | fleet>
+owner: <spec author>                   # instances NEVER edit this file
+updated: <YYYY-MM-DD>
+status: UNSEEDED
+---
+# SOP — <kind>
+<!-- The TEMPLATE half: how this KIND of thing does its job, anywhere it is
+     instantiated. Absorbs the static role file at seat altitude. Instance-local
+     knowledge belongs in LEARNED.md beside this, never here. -->
+
+## PURPOSE
+<!-- what this kind exists to do -->
+
+## CORE LOOP
+<!-- the job's shape: inputs → work → outputs/handoffs -->
+
+## DEFAULT PRACTICES
+<!-- each with its reason attached -->
+- 
+
+## BOUNDARIES
+<!-- what this kind never does; where its authority ends -->
+- 

package/daemon/context-packs/skills/openrig-operating-model/templates/SPEC.md

@@ -0,0 +1,54 @@
+---
+node: <project | mission | slice>
+intent: >-
+  <ONE sentence: what this node is FOR. This composes UP the chain, so write it to be
+   read from below by someone standing on a slice. Say the purpose, never the location —
+   "deferred features land here" is a routing rule and orients nobody.>
+id: <OPR.x.y[.n] — minted by the PM; omit if unminted>
+stage: wip
+# stage: wip | provisional | established | canonical | superseded | retired
+status: UNSEEDED
+---
+
+<!-- ONE authored file per work node. README.md and IMPLEMENTATION-PRD.md fold into this.
+     PROOF.md stays separate and is good. PROGRESS.md is the authored acceptance checklist:
+     checkbox items are stored marks; every roll-up above them is derived, never hand-authored.
+     Legacy README.md nodes stay valid indefinitely; nothing is forced to migrate.
+
+     PROJECT and MISSION nodes: the frontmatter `intent:` IS the whole job. A mission
+     ORGANISES slices and carries the context they need; it specifies nothing. Keep the
+     body short or delete it — everything below this line is for SLICES.
+
+     WHATEVER BODY YOU DO WRITE, two tests per sentence:
+       PORTABILITY — if it would read correctly on a stranger's machine it is knowledge
+         about a KIND; it belongs in the operating-model skill, not on the tree.
+       VOLATILITY — a SHA, a count, a status, a roster: write the COMMAND that derives it,
+         never the answer. A value here is stale by the next fold.
+     And check the tree: traps and how-we-work live in LEARNED.md on the topology tree,
+     not here. This file is what is being BUILT.
+
+     SLICE nodes are the ONLY altitude that specifies. Keep the sections you need and
+     delete the rest; this is a starting shape, not a contract. Under the FACTORY operating
+     model this node also carries mini-requirements and a proof contract — see that mode's
+     plugin. Under the LAB it does not. -->
+
+# <name>
+
+## What must be built
+
+<!-- The change itself, at the altitude a builder can act on. -->
+
+## Why this is the shape
+
+<!-- The reasoning a reader would otherwise have to reconstruct — especially any option
+     considered and rejected. This is the part that survives you. -->
+
+## How we will know it works
+
+<!-- Verified by EFFECT: run it, look at the result. Name the command and what it should
+     print, not the feeling of being done. -->
+
+## Scope fences
+
+<!-- What this deliberately does NOT include, so it neither swallows the release nor grows
+     during the build. Fences written after the fact are excuses; written now they hold. -->