@openrig/cli 0.5.4 → 0.5.6

package/daemon/context-packs/skills/pm/plan-review/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "plan-review"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Multi-perspective review of a feature plan or requirements doc before development begins. Evaluates from strategy, design/UX, and engineering angles to catch gaps early."
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/pm/requirements-writer/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "requirements-writer"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Conversational intake that produces a structured requirements.md following a standardized PM schema. Enforces PM lane — no architecture, no estimates, no implementation details. Uses GIVEN/WHEN/THEN acceptance criteria."
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/pm/ui-mockup/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "ui-mockup"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing."
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/pods/development-team/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "development-team"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "How the development pod coordinates implementation, QA, and design without skipping gates."
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/pods/orchestration-team/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "orchestration-team"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Operating manual for the orchestration pod. Covers lead vs peer roles, monitoring with rig commands, permission handling, implementation pair gating, dogfood loops, review routing, agent behavioral models, intervention discipline, and communication culture."
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/pods/oversight-team/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "oversight-team"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention ladder (orchestrator-ping -> refocus -> human escalation), and the cheap+deep model economics. NOT for orchestrating your OWN rig (orchestration-team) and NOT the intervention primi"
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/pods/review-team/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "review-team"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Complete operating manual for the review pod. Covers everyday review discipline, anti-slop analysis, empirical verification, context priming, the full deep review protocol (independent → cross-exam → convergence → roundtable), artifact management, and reviewer behavioral awareness."
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/agent-browser/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "agent-browser"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction."
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/brainstorming/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "brainstorming"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/context-engineering/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "context-engineering"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Use when designing, reviewing, or debugging how an agent's context window gets filled, pruned, or shared — choosing what loads at boot versus on demand, sizing an install or an always-loaded file, fixing an agent that drifts, repeats itself, or forgets constraints mid-task, planning compaction or summarization, deciding single-agent versus subagents, engineering handoffs between agents, or picking a tool loadout. NOT for rewording a prompt's tone, choosing which model to pin, or debugging busine"
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/dogfood/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "dogfood"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app/site/platform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams."
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/executing-plans/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "executing-plans"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Use when you have a written implementation plan to execute in a separate session with review checkpoints"
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/frontend-design/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "frontend-design"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics."
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/systematic-debugging/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "systematic-debugging"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes"
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/test-driven-development/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "test-driven-development"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Use when implementing any feature or bugfix, before writing implementation code"
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/using-superpowers/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "using-superpowers"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions"
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/verification-before-completion/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "verification-before-completion"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always"
 files:
   - path: "SKILL.md"

package/daemon/context-packs/skills/process/writing-plans/manifest.yaml

@@ -1,7 +1,8 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "writing-plans"
-version: "0.5.4"
+version: "0.5.6"
+taxonomy: "skills"
 purpose: "Use when you have a spec or requirements for a multi-step task, before touching code"
 files:
   - path: "SKILL.md"

package/daemon/context-packs/world-example/manifest.yaml

@@ -0,0 +1,21 @@
+name: world-example
+version: "0.5.6"
+taxonomy: world
+purpose: "A fill-in template showing the anatomy of an OpenRig world pack."
+files:
+  - path: your-world.md
+    role: world
+    summary: "A minimal fill-in template for describing an agent's world."
+atoms:
+  - id: your-world
+    address: your-world.md
+    taxonomy: world
+    regions: [identity, ontology, terrain, actors, laws, history, state, affordances]
+    situations: [fresh, handover, post-compaction]
+    purpose: depth
+    runtime: any
+    order: 10
+    priority: core
+    probe:
+      prompt: "Describe the operating world for a book-writing project."
+      expect: "The agent fills one coherent world file and derives volatile state instead of creating a folder per region."

package/daemon/context-packs/world-example/your-world.md

@@ -0,0 +1,54 @@
+# Your world
+
+<!-- world-claim: world-example-purpose -->
+A world pack situates an agent: it describes where the agent is, what exists there, and how to act.
+<!-- world-claim: world-example-install -->
+Use `rig context add <pack-directory>` to install a world pack, confirm its ref with `rig context list`, and derive the configured store with `rig config get context.packs_root` only when a path is needed.
+
+<!-- world-claim: world-example-authoring -->
+Copy this pack, update its manifest, and replace each prompt below with your world's facts.
+
+## Exercise: Book world
+
+<!-- world-claim: world-example-book-exercise -->
+Run `rig context get world-example`, copy this pack, and make the project a book world by describing the writer, manuscript, sources, editorial rules, decisions, current draft state, and next useful actions in a few coherent files.
+
+<!-- world-claim: world-example-regions -->
+The region names below are atom metadata, not a required directory layout.
+
+## Identity
+
+Name the world and the agent's place in it.
+
+## Ontology
+
+Define the important kinds of things and what each is for.
+
+## Actors
+
+Name who else is present, what they own, and how to reach them.
+
+## Terrain
+
+Map where code, records, documentation, and operational surfaces live.
+
+## Laws
+
+State the durable rules and precedence that govern action here.
+
+## History
+
+Record prior decisions and events that explain the world's current shape.
+
+## State
+
+Point to commands or sources that derive what is true right now.
+
+## Affordances
+
+List what the agent can do and the trigger for reaching each capability.
+
+## Checks
+
+<!-- world-claim: world-example-checks -->
+For every checkable authored claim, add a named check that can fail; flag taste or genuinely unverifiable claims instead of dressing judgment up as a test; and derive paths, counts, inventories, and live state from commands rather than copying current answers into this file.

package/daemon/context-packs/world-public/boundaries.md

@@ -0,0 +1,33 @@
+# Boundaries
+
+## This pack covers
+
+<!-- world-claim: boundary-coverage -->
+This public pack covers only the shared world structure and discovery surfaces listed below.
+
+- the stable separation between world, lore, skills, and mission context;
+- the eight world regions as atom metadata;
+- the author-versus-derive rule;
+- a small convention for authoring and checking a world;
+- the live commands needed to discover identity, topology, packs, and command help.
+
+## This pack does not cover
+
+<!-- world-claim: boundary-exclusions -->
+This public pack does not supply rig-specific reality, current work, local lore, repository instructions, or irreversible judgment.
+
+- the purpose, actors, topology, paths, or current state of a particular rig;
+- the mission you currently own;
+- local lore earned by a seat or team;
+- harness-specific repository instructions;
+- irreversible product or operator judgment.
+
+<!-- world-claim: boundary-guidance -->
+These gaps are not omissions to fill with plausible prose: read the local world, mission, lore, repository instructions, and live command surfaces, then ask the decision owner when no source can answer.
+
+## Namespace edge
+
+<!-- world-claim: private-ref-boundary -->
+Private world installs remain rig-local under their own refs and are never shadowed by this builtin.
+This pack is `world-public`. A local world may use a different ref and carry instance-specific
+substance without inheriting or being replaced by these public bytes.

package/daemon/context-packs/world-public/build-your-world.md

@@ -0,0 +1,84 @@
+# Build your world
+
+## Keep the first version small
+
+<!-- world-claim: minimal-world-layout -->
+Start with a directory whose name says what world it serves:
+
+```text
+book-world/
+  manifest.yaml
+  world.md
+  boundaries.md
+```
+
+<!-- world-claim: authoring-convention -->
+The manifest names the files. The prose states durable purpose, relationships, and what to trust. Add atoms when the same bytes need situation, runtime, order, or region metadata. Add a claim ledger and verifier when authored statements can drift into consequential lies. Do not add ceremony that has no reader yet.
+
+## Separate kinds, tag regions
+
+<!-- world-claim: context-kinds -->
+WORLD + LORE + SKILLS + MISSION is the top-level separation of context kinds.
+
+- WORLD: where the agent is — entities, relationships, rules, history, state sources, affordances.
+- LORE: what a position learned by living there.
+- SKILLS: repeatable procedural capability.
+- MISSION: the current work and why it matters.
+
+<!-- world-claim: regions-are-tags -->
+The eight regions are metadata on atoms, not a required folder tree.
+Tag existing authored files with identity, ontology, terrain, actors, laws, history, state, and
+affordances. One coherent file may cover several regions; do not fork the same idea into eight
+copies.
+
+## Carry an honest coverage map
+
+Inspect the public pack and compose it for a fresh session:
+
+```bash
+rig context get world-public
+rig context profile world-public --situation fresh
+```
+
+<!-- world-claim: retrieve-public-pack -->
+Use `rig context get world-public` to retrieve the assembled public pack bytes.
+
+<!-- world-claim: compose-fresh-profile -->
+Use `rig context profile world-public --situation fresh` to compose its fresh-session atom graph.
+
+<!-- world-claim: region-metadata -->
+The regions field says which dimensions an atom covers; atoms carry it as manifest metadata, and consumers may filter that metadata as data.
+<!-- world-claim: no-region-selector -->
+This pack promises no region selector or subset-composition operation.
+If a real consumer needs region-subset composition, route that
+capability as separate profile-composer work.
+
+<!-- world-claim: derived-reading-cost -->
+The reading cost is derived when a profile is composed, not copied into this pack.
+Use the composed profile's reported token total to decide what a future consumer should request; do not cut sentences until
+their meaning breaks.
+
+## Exercise: Book world
+
+<!-- world-claim: book-example-purpose -->
+The exercise uses a book because the model's existing world-building fluency needs the least translation there, and a reader with no software context is the hardest stranger case.
+
+<!-- world-claim: retrieve-world-example -->
+Use `rig context get world-example` to retrieve the worked book-world template.
+
+<!-- world-claim: book-exercise-guidance -->
+Use the example to describe who the writer is, what manuscripts and sources exist, where they live, which editorial rules apply, what decisions shaped the draft, how current state is derived, and what the agent can do next; keep it pleasant to read, and simplify it if the arrangement feels like a filing system rather than a place.
+
+<!-- world-claim: book-to-software -->
+The book exercise maps its manuscript to a codebase, editorial rules to engineering laws and conventions, draft state to derived build and deploy state, and its writer to the team. Software worlds use the same moves.
+
+<!-- world-claim: software-shaped-bridge -->
+Agents already know software-shaped building through specifications, verification loops, tooling, and the programming substrate. A world pack built this way uses named files and a manifest as the spec shape, per-claim checks and a verifier that can fail as the test suite, and derive-at-source commands as the feedback loop. A blank-slate reader therefore already knows how to build this kind of artifact: world-building supplies the information architecture while software-shaping supplies buildability.
+
+<!-- world-claim: optional-claim-checking-climb -->
+The full public pack demonstrates the optional claim-checking climb.
+
+<!-- world-claim: derive-pack-path -->
+Use rig context show world-public --json to derive the installed pack directory.
+<!-- world-claim: run-public-verifier -->
+Run `sh verify-world.sh` in that derived directory instead of teaching a machine-specific path.

package/daemon/context-packs/world-public/claims.yaml

@@ -0,0 +1,205 @@
+claims:
+  - id: world-purpose
+    statement: "A world states the durable operating reality an agent needs before it can act well."
+    kind: judgment
+    flagged: "Authored purpose and taste; no live scan can prove it."
+  - id: author-derive-rule
+    statement: "Supply the authored relationships no inventory can discover, point at commands for facts that change, and do not memorize a roster, path, count, status, or command list when the live system can answer."
+    kind: structural
+    check: author-derive-rule
+  - id: derive-identity
+    statement: "Use rig whoami --json to derive the identity of the seat you actually occupy."
+    kind: operational
+    check: derive-identity
+  - id: derive-topology
+    statement: "Use rig ps --nodes --json to derive which seats exist in the rig you occupy now."
+    kind: operational
+    check: derive-topology
+  - id: discover-context
+    statement: "Use rig context list to discover the context packs available on this installation."
+    kind: operational
+    check: rig-command-surface
+  - id: discover-commands
+    statement: "Use rig --help before inventing a command or wrapper."
+    kind: operational
+    check: rig-command-surface
+  - id: trust-source-table
+    statement: "Each trust question below names its authoritative source, and a disagreement between authored intent and live state must be investigated rather than silently resolved for convenience."
+    kind: structural
+    check: trust-source-table
+  - id: agents-complement
+    statement: "If a repository uses AGENTS.md, keep repo instructions there; a world complements those instructions."
+    kind: structural
+    check: agents-md-complement
+  - id: minimal-world-layout
+    statement: "Start with a directory whose name says what world it serves:"
+    kind: judgment
+    flagged: "Authored starting-point guidance; no live scan can prove it is the best first shape."
+  - id: authoring-convention
+    statement: "The manifest names the files. The prose states durable purpose, relationships, and what to trust. Add atoms when the same bytes need situation, runtime, order, or region metadata. Add a claim ledger and verifier when authored statements can drift into consequential lies. Do not add ceremony that has no reader yet."
+    kind: structural
+    check: authoring-convention
+  - id: context-kinds
+    statement: "WORLD + LORE + SKILLS + MISSION is the top-level separation of context kinds."
+    kind: structural
+    check: taxonomy-layout
+  - id: regions-are-tags
+    statement: "The eight regions are metadata on atoms, not a required folder tree."
+    kind: structural
+    check: atom-regions
+  - id: retrieve-public-pack
+    statement: "Use `rig context get world-public` to retrieve the assembled public pack bytes."
+    kind: operational
+    check: retrieve-public-pack
+  - id: compose-fresh-profile
+    statement: "Use `rig context profile world-public --situation fresh` to compose its fresh-session atom graph."
+    kind: operational
+    check: compose-fresh-profile
+  - id: region-metadata
+    statement: "The regions field says which dimensions an atom covers; atoms carry it as manifest metadata, and consumers may filter that metadata as data."
+    kind: structural
+    check: atom-regions
+  - id: no-region-selector
+    statement: "This pack promises no region selector or subset-composition operation."
+    kind: structural
+    check: no-region-selector
+  - id: derived-reading-cost
+    statement: "The reading cost is derived when a profile is composed, not copied into this pack."
+    kind: structural
+    check: derived-reading-cost
+  - id: book-example-purpose
+    statement: "The exercise uses a book because the model's existing world-building fluency needs the least translation there, and a reader with no software context is the hardest stranger case."
+    kind: judgment
+    flagged: "Authored purpose and taste; no live scan can prove it."
+  - id: retrieve-world-example
+    statement: "Use `rig context get world-example` to retrieve the worked book-world template."
+    kind: operational
+    check: retrieve-world-example
+  - id: book-exercise-guidance
+    statement: "Use the example to describe who the writer is, what manuscripts and sources exist, where they live, which editorial rules apply, what decisions shaped the draft, how current state is derived, and what the agent can do next; keep it pleasant to read, and simplify it if the arrangement feels like a filing system rather than a place."
+    kind: judgment
+    flagged: "Authored exercise and taste guidance; no live scan can prove it."
+  - id: book-to-software
+    statement: "The book exercise maps its manuscript to a codebase, editorial rules to engineering laws and conventions, draft state to derived build and deploy state, and its writer to the team. Software worlds use the same moves."
+    kind: judgment
+    flagged: "Authored purpose and taste; no live scan can prove it."
+  - id: software-shaped-bridge
+    statement: "Agents already know software-shaped building through specifications, verification loops, tooling, and the programming substrate. A world pack built this way uses named files and a manifest as the spec shape, per-claim checks and a verifier that can fail as the test suite, and derive-at-source commands as the feedback loop. A blank-slate reader therefore already knows how to build this kind of artifact: world-building supplies the information architecture while software-shaping supplies buildability."
+    kind: judgment
+    flagged: "Authored analogy and purpose; no live scan can prove it."
+  - id: optional-claim-checking-climb
+    statement: "The full public pack demonstrates the optional claim-checking climb."
+    kind: structural
+    check: authoring-convention
+  - id: derive-pack-path
+    statement: "Use rig context show world-public --json to derive the installed pack directory."
+    kind: operational
+    check: derive-pack-path
+  - id: run-public-verifier
+    statement: "Run `sh verify-world.sh` in that derived directory instead of teaching a machine-specific path."
+    kind: operational
+    check: run-public-verifier
+  - id: boundary-coverage
+    statement: "This public pack covers only the shared world structure and discovery surfaces listed below."
+    kind: structural
+    check: boundary-coverage
+  - id: boundary-exclusions
+    statement: "This public pack does not supply rig-specific reality, current work, local lore, repository instructions, or irreversible judgment."
+    kind: structural
+    check: boundary-exclusions
+  - id: boundary-guidance
+    statement: "These gaps are not omissions to fill with plausible prose: read the local world, mission, lore, repository instructions, and live command surfaces, then ask the decision owner when no source can answer."
+    kind: judgment
+    flagged: "Authored boundary guidance; no live scan can decide when a gap requires owner judgment."
+  - id: private-ref-boundary
+    statement: "Private world installs remain rig-local under their own refs and are never shadowed by this builtin."
+    kind: structural
+    check: private-ref-boundary
+  - id: world-example-purpose
+    statement: "A world pack situates an agent: it describes where the agent is, what exists there, and how to act."
+    kind: judgment
+    flagged: "Authored purpose and taste; no live scan can prove it."
+  - id: world-example-install
+    statement: "Use `rig context add <pack-directory>` to install a world pack, confirm its ref with `rig context list`, and derive the configured store with `rig config get context.packs_root` only when a path is needed."
+    kind: operational
+    check: world-example-install
+  - id: world-example-authoring
+    statement: "Copy this pack, update its manifest, and replace each prompt below with your world's facts."
+    kind: structural
+    check: world-example-consistency
+  - id: world-example-book-exercise
+    statement: "Run `rig context get world-example`, copy this pack, and make the project a book world by describing the writer, manuscript, sources, editorial rules, decisions, current draft state, and next useful actions in a few coherent files."
+    kind: structural
+    check: world-example-consistency
+  - id: world-example-regions
+    statement: "The region names below are atom metadata, not a required directory layout."
+    kind: structural
+    check: world-example-consistency
+  - id: world-example-checks
+    statement: "For every checkable authored claim, add a named check that can fail; flag taste or genuinely unverifiable claims instead of dressing judgment up as a test; and derive paths, counts, inventories, and live state from commands rather than copying current answers into this file."
+    kind: structural
+    check: world-example-consistency
+  - id: public-manifest-purpose
+    statement: "A portable operating-world primer that derives volatile facts and teaches agents to author their own world."
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-summary-start-here
+    statement: "Derive where you are, what to trust, and which context belongs in a world."
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-summary-build-your-world
+    statement: "The minimal authoring convention and a book-world exercise."
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-summary-boundaries
+    statement: "What this public world covers, excludes, and cannot decide."
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-summary-claims
+    statement: "Every authored claim mapped to a failing check or an explicit honesty flag."
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-summary-verify-world
+    statement: "Portable named checks with loud failures and skips."
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-probe-enter-the-world-prompt
+    statement: "You just arrived in an unfamiliar OpenRig environment. What do you derive before acting?"
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-probe-enter-the-world-expect
+    statement: "The agent derives its identity, live topology, available context, and command surface instead of guessing."
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-probe-author-a-world-prompt
+    statement: "Create a world for a book-writing project without turning the eight regions into folders."
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-probe-author-a-world-expect
+    statement: "The agent starts with a small manifest and authored files, tags atoms by region, and keeps other context kinds separate."
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-probe-know-the-edges-prompt
+    statement: "Which gaps can this public world answer, and which still require local sources or human judgment?"
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: public-manifest-probe-know-the-edges-expect
+    statement: "The agent distinguishes public structure from rig-local facts, current state, mission context, and irreversible judgment."
+    kind: structural
+    check: public-manifest-authored-claims
+  - id: example-manifest-purpose
+    statement: "A fill-in template showing the anatomy of an OpenRig world pack."
+    kind: structural
+    check: example-manifest-authored-claims
+  - id: example-manifest-summary-your-world
+    statement: "A minimal fill-in template for describing an agent's world."
+    kind: structural
+    check: example-manifest-authored-claims
+  - id: example-manifest-probe-your-world-prompt
+    statement: "Describe the operating world for a book-writing project."
+    kind: structural
+    check: example-manifest-authored-claims
+  - id: example-manifest-probe-your-world-expect
+    statement: "The agent fills one coherent world file and derives volatile state instead of creating a folder per region."
+    kind: structural
+    check: example-manifest-authored-claims