opennori 0.1.1 → 0.1.3

package/.opennori/protocol.md

@@ -38,10 +38,10 @@ current gap, risk gate, and report.
 | ID | Tool / entrypoint | User operation | User acceptance criterion | Passing threshold |
 | --- | --- | --- | --- | --- |
 | AC-P-1 | Editor / file browser | Open the active Nori Contract | The user understands goal, layered ACs, each status, and the current gap. | No chat history or implementation explanation required; understandable within 60 seconds. |
-| AC-P-2 | CLI | Run `nori check` | The user can reject technical implementation details masquerading as ACs. | Files, fields, commands, tests, or modules cannot be accepted as user ACs by themselves. |
-| AC-P-3 | CLI | Run `nori next` or `nori status` | The user sees the current acceptance gap and completion answer, not a process-step list. | Output answers which AC is missing, whether complete, and whether human action is required. |
+| AC-P-2 | CLI | Run `opennori check` | The user can reject technical implementation details masquerading as ACs. | Files, fields, commands, tests, or modules cannot be accepted as user ACs by themselves. |
+| AC-P-3 | CLI | Run `opennori next` or `opennori status` | The user sees the current acceptance gap and completion answer, not a process-step list. | Output answers which AC is missing, whether complete, and whether human action is required. |
 | AC-P-4 | CLI / report | Inspect a high-risk AC | The user sees that weak evidence cannot make it passing. | High-risk passing cannot rely only on agent self-summary. |
-| AC-P-5 | CLI / Codex | Trigger `nori report` | The user sees goal, layered AC statuses, evidence summaries, current gap, intervention, and conclusion. | Report is organized by acceptance state and evidence, not process steps. |
+| AC-P-5 | CLI / Codex | Trigger `opennori report` | The user sees goal, layered AC statuses, evidence summaries, current gap, intervention, and conclusion. | Report is organized by acceptance state and evidence, not process steps. |
 | AC-P-6 | CLI / report | Inspect evidence basis | The user can tell what evidence supports passing, blocked, or waived ACs. | Report/status shows evidence summary, basis, confidence, and limitations, not only an agent conclusion. |
 | AC-P-7 | CLI / report | Review evidence sources | The user can review evidence sources without constraining how the agent gathered them. | Sources can be commands, artifacts, URLs, screenshots, diffs, human confirmations, or other reviewable references. |
 | AC-P-8 | CLI / report | Compare evidence basis types | The user can distinguish tool observations, human confirmations, artifact reviews, protocol checks, and agent observations. | Evidence basis is shown clearly and agent judgment is not disguised as tool or human verification. |
@@ -71,18 +71,18 @@ a durable workflow asset.
 
 | ID | Tool / entrypoint | User operation | User acceptance criterion | Passing threshold |
 | --- | --- | --- | --- | --- |
-| AC-Z-1 | CLI | Run `nori skill export` | The user gets a usable Codex Skill draft for OpenNori. | The Skill tells agents to drive work through resume, next, evidence, evaluate, status, and report. |
-| AC-Z-2 | CLI | Run `nori install` | The user can install OpenNori into a project without unexpected overwrites. | Install shows created/skipped assets; existing user content is not overwritten by default. |
+| AC-Z-1 | CLI | Run `opennori skill export` | The user gets a usable Codex Skill draft for OpenNori. | The Skill tells agents to drive work through resume, next, evidence, evaluate, status, and report. |
+| AC-Z-2 | CLI | Run `opennori install` | The user can install OpenNori into a project without unexpected overwrites. | Install shows created/skipped assets; existing user content is not overwritten by default. |
 | AC-Z-3 | Git / PR diff | Review the agent's changes | The user can separate acceptance evidence changes from implementation noise. | Summary defaults to AC status changes, evidence changes, and user impact. |
-| AC-Z-4 | CLI | Run `nori list` and select a goal | The user can see multiple active goals and choose one explicitly. | Multiple active goals are listed with status, gap, and paths; `--goal` selects the target. |
+| AC-Z-4 | CLI | Run `opennori list` and select a goal | The user can see multiple active goals and choose one explicitly. | Multiple active goals are listed with status, gap, and paths; `--goal` selects the target. |
 | AC-Z-5 | CLI | Archive a completed or blocked goal | The user removes it from active work while preserving evidence and report. | Active no longer lists the goal; contract, ledger, and report remain recoverable. |
 | AC-Z-6 | Project file browser | Inspect the project after running OpenNori | The user sees OpenNori-owned state under `.opennori/` instead of a generic project `process/` directory. | Install, draft, brainstorm, report, and archive write OpenNori state under `.opennori/` by default. |
-| AC-Z-7 | CLI / project file browser | Run `nori install` | The user can inspect project OpenNori registration and judge version, managed entries, active goals, Skill status, and protocol capabilities. | Install output uses create, skip, overwrite, or update semantics; `.opennori/manifest.json` records version, managed files, active goals, Skill state, and capabilities. |
-| AC-Z-8 | CLI | Run `nori doctor` | The user can judge whether the project is `ready`, `needs-action`, or `broken`, and see the next recovery action. | Doctor checks `.opennori` structure, manifest consistency, active goal recoverability, Skill sync, CLI runtime, and recovery suggestions. |
-| AC-Z-9 | CLI | Preview install with `nori install --dry-run` | The user can judge what OpenNori would create, skip, update, or overwrite before writing to the project. | Install plan lists action, kind, managed status, write intent, destructive flag, and reason; dry-run reports zero actual writes. |
-| AC-Z-10 | CLI | Apply force install | The user must preview and explicitly confirm destructive install actions before files are overwritten. | Real `nori install --force` fails without confirmation; dry-run previews destructive overwrites; confirmed force install may write. |
+| AC-Z-7 | CLI / project file browser | Run `opennori install` | The user can inspect project OpenNori registration and judge version, managed entries, active goals, Skill status, and protocol capabilities. | Install output uses create, skip, overwrite, or update semantics; `.opennori/manifest.json` records version, managed files, active goals, Skill state, and capabilities. |
+| AC-Z-8 | CLI | Run `opennori doctor` | The user can judge whether the project is `ready`, `needs-action`, or `broken`, and see the next recovery action. | Doctor checks `.opennori` structure, manifest consistency, active goal recoverability, Skill sync, CLI runtime, and recovery suggestions. |
+| AC-Z-9 | CLI | Preview install with `opennori install --dry-run` | The user can judge what OpenNori would create, skip, update, or overwrite before writing to the project. | Install plan lists action, kind, managed status, write intent, destructive flag, and reason; dry-run reports zero actual writes. |
+| AC-Z-10 | CLI | Apply force install | The user must preview and explicitly confirm destructive install actions before files are overwritten. | Real `opennori install --force` fails without confirmation; dry-run previews destructive overwrites; confirmed force install may write. |
 | AC-Z-11 | CLI | Preview and apply uninstall | The user can uninstall OpenNori entry assets without losing acceptance state by default. | Uninstall plan shows removals and preserved state; real uninstall requires confirmation; `.opennori` state is deleted only with `--include-state --confirm`. |
-| AC-Z-12 | CLI / Codex Skills | Install OpenNori Skill Pack | The agent gets focused OpenNori Skills for acceptance, evidence, Nori Profile, project health, and reporting while the user keeps using natural language. | `nori skill export --pack` exposes the pack; `nori install --skill` writes it; manifest records `skill_pack`; doctor detects missing or stale pack Skills. |
+| AC-Z-12 | CLI / Codex Skills | Install OpenNori Skill Pack | The agent gets focused OpenNori Skills for acceptance, evidence, Nori Profile, project health, and reporting while the user keeps using natural language. | `opennori skill export --pack` exposes the pack; `opennori install --skill` writes it; manifest records `skill_pack`; doctor detects missing or stale pack Skills. |
 
 ## Required Artifact Pair
 
@@ -116,10 +116,10 @@ Each active goal has:
 - optional repo-local OpenNori Skill Pack state
 - protocol capabilities exposed by this CLI
 
-`nori install` creates or refreshes the manifest. State-changing OpenNori commands refresh it when
+`opennori install` creates or refreshes the manifest. State-changing OpenNori commands refresh it when
 `.opennori/` already exists.
 
-`nori install --dry-run` returns an install plan. The plan uses deterministic action semantics:
+`opennori install --dry-run` returns an install plan. The plan uses deterministic action semantics:
 
 - `create`: missing OpenNori asset would be created
 - `exists`: required OpenNori directory already exists
@@ -130,11 +130,11 @@ Each active goal has:
 Each planned action also reports `kind`, `managed`, `would_write`, `will_write`, `destructive`,
 and a short human-readable reason.
 
-Real `nori install --force` can overwrite OpenNori-managed files, so it requires explicit confirmation.
-Run `nori install --dry-run --force` first to inspect destructive actions, then rerun with
+Real `opennori install --force` can overwrite OpenNori-managed files, so it requires explicit confirmation.
+Run `opennori install --dry-run --force` first to inspect destructive actions, then rerun with
 `--confirm` only if those writes are acceptable.
 
-`nori uninstall --dry-run` returns an uninstall plan. By default it removes entry assets such as the
+`opennori uninstall --dry-run` returns an uninstall plan. By default it removes entry assets such as the
 repo-local OpenNori Skill and manifest, while preserving Nori Contracts, evidence records,
 reports, archives, and brainstorms. Real uninstall requires `--confirm`. Deleting the whole `.opennori`
 state directory requires both `--include-state` and `--confirm`.
@@ -151,8 +151,8 @@ the root `nori` Skill routes natural-language requests to focused Skills:
 - `nori-project-health`: install, uninstall, doctor, manifest, and Skill Pack sync
 - `nori-reporting`: status, report, current gap, user intervention, and changes
 
-`nori install --skill` installs the pack under `.agents/skills/`. The manifest records `skill_pack`
-state, and `nori doctor` checks whether the pack is installed and in sync.
+`opennori install --skill` installs the pack under `.agents/skills/`. The manifest records `skill_pack`
+state, and `opennori doctor` checks whether the pack is installed and in sync.
 
 ## Nori Profile
 
@@ -179,7 +179,7 @@ Completion rules:
 - `avoid` blocks completion if violated.
 
 Agents translate the user's natural-language preferences into profile records. Users should not
-need to remember `nori profile` commands.
+need to remember `opennori profile` commands.
 
 ## Status Model
 
@@ -239,34 +239,34 @@ all evidence through a narrow adapter taxonomy.
 
 On every turn:
 
-1. If the user wants to discuss, brainstorm, explore, or is not ready to define acceptance criteria, run `nori brainstorm --idea "<idea>" --root <repo> --json`.
+1. If the user wants to discuss, brainstorm, explore, or is not ready to define acceptance criteria, run `opennori brainstorm --idea "<idea>" --root <repo> --json`.
 2. Show only candidate acceptance directions and ask the user to choose or revise a direction. Brainstorm output is not a contract or completion evidence.
-3. If the user chooses a candidate, run `nori draft --from-brainstorm <brainstorm-id> --candidate <A|B|C> --root <repo> --json`.
-4. If the user starts with "use OpenNori" / "用 OpenNori 跑这个任务", run `nori draft --goal "<goal>" --root <repo> --json`.
+3. If the user chooses a candidate, run `opennori draft --from-brainstorm <brainstorm-id> --candidate <A|B|C> --root <repo> --json`.
+4. If the user starts with "use OpenNori" / "用 OpenNori 跑这个任务", run `opennori draft --goal "<goal>" --root <repo> --json`.
 5. Show the draft acceptance criteria and ask the user to approve or revise them.
-6. After approval, run `nori approve --root <repo> --summary "<approval>" --json`.
-7. If the user states required Skills, preferred stacks, avoided tools, install policy, or execution constraints, run `nori profile add --root <repo> ... --json` and keep those items out of the user acceptance criteria.
-8. If the user revises a criterion later, run `nori criterion update --root <repo> --criterion <id> ... --json`; old evidence for the changed criterion is cleared.
-9. Run `nori resume --root <repo>` or `nori next --root <repo>` to recover the active goal and current acceptance gap from repository files.
+6. After approval, run `opennori approve --root <repo> --summary "<approval>" --json`.
+7. If the user states required Skills, preferred stacks, avoided tools, install policy, or execution constraints, run `opennori profile add --root <repo> ... --json` and keep those items out of the user acceptance criteria.
+8. If the user revises a criterion later, run `opennori criterion update --root <repo> --criterion <id> ... --json`; old evidence for the changed criterion is cleared.
+9. Run `opennori resume --root <repo>` or `opennori next --root <repo>` to recover the active goal and current acceptance gap from repository files.
 10. Work only to produce evidence for that gap.
-11. Add acceptance evidence with `nori evidence add`; choose any suitable verification method, but record basis, sources, reviewability, confidence, and limitations. Add profile compliance evidence with `nori profile evidence` when profile items exist.
-12. Run `nori evaluate`.
+11. Add acceptance evidence with `opennori evidence add`; choose any suitable verification method, but record basis, sources, reviewability, confidence, and limitations. Add profile compliance evidence with `opennori profile evidence` when profile items exist.
+12. Run `opennori evaluate`.
 13. Report acceptance state, profile compliance, and evidence, not implementation steps.
 
 Useful commands:
 
-- `nori brainstorm --idea "<idea>" --root <repo>`: create selectable acceptance directions before a contract exists.
-- `nori draft --goal "<goal>" --root <repo>`: create a draft Nori Contract that needs user approval.
-- `nori draft --from-brainstorm <brainstorm-id> --candidate <A|B|C> --root <repo>`: convert a selected brainstorm direction into a draft contract.
-- `nori approve --root <repo>`: mark the acceptance basis as approved so completion can be decided.
-- `nori criterion update --root <repo> --criterion <id> ...`: preserve a user revision as the new acceptance basis.
-- `nori evidence add --root <repo> --criterion <id> --kind <kind> --summary "<summary>" --result <passing|failing|blocked|waived> --basis <basis> --source '<json-or-label>' --reviewability "<how to review>" --limitations "<known limits>"`: attach user-understandable, reviewable evidence without forcing a fixed adapter.
-- `nori profile add --root <repo> --type <skill|stack|constraint> --name "<name>" --strength <must|prefer|avoid>`: record user execution preferences separately from ACs.
-- `nori profile evidence --root <repo> --item <item-id> --result <satisfied|violated|waived>`: record whether the agent followed the profile.
-- `nori profile show --root <repo>`: show profile compliance and blocking items.
-- `nori list --root <repo>`: list active OpenNori goals.
-- `nori install --root <repo>`: create or refresh project-local OpenNori assets and manifest.
-- `nori doctor --root <repo>`: inspect project OpenNori health and recovery actions.
-- `nori resume --root <repo>`: recover the active goal, current gap, completion answer, and intervention state.
-- `nori status --root <repo>`: answer whether the goal is complete and whether the user needs to act.
-- `nori report --root <repo>`: generate the human acceptance report.
+- `opennori brainstorm --idea "<idea>" --root <repo>`: create selectable acceptance directions before a contract exists.
+- `opennori draft --goal "<goal>" --root <repo>`: create a draft Nori Contract that needs user approval.
+- `opennori draft --from-brainstorm <brainstorm-id> --candidate <A|B|C> --root <repo>`: convert a selected brainstorm direction into a draft contract.
+- `opennori approve --root <repo>`: mark the acceptance basis as approved so completion can be decided.
+- `opennori criterion update --root <repo> --criterion <id> ...`: preserve a user revision as the new acceptance basis.
+- `opennori evidence add --root <repo> --criterion <id> --kind <kind> --summary "<summary>" --result <passing|failing|blocked|waived> --basis <basis> --source '<json-or-label>' --reviewability "<how to review>" --limitations "<known limits>"`: attach user-understandable, reviewable evidence without forcing a fixed adapter.
+- `opennori profile add --root <repo> --type <skill|stack|constraint> --name "<name>" --strength <must|prefer|avoid>`: record user execution preferences separately from ACs.
+- `opennori profile evidence --root <repo> --item <item-id> --result <satisfied|violated|waived>`: record whether the agent followed the profile.
+- `opennori profile show --root <repo>`: show profile compliance and blocking items.
+- `opennori list --root <repo>`: list active OpenNori goals.
+- `opennori install --root <repo>`: create or refresh project-local OpenNori assets and manifest.
+- `opennori doctor --root <repo>`: inspect project OpenNori health and recovery actions.
+- `opennori resume --root <repo>`: recover the active goal, current gap, completion answer, and intervention state.
+- `opennori status --root <repo>`: answer whether the goal is complete and whether the user needs to act.
+- `opennori report --root <repo>`: generate the human acceptance report.

package/README.md

@@ -1,12 +1,50 @@
 # OpenNori
 
-OpenNori.
+OpenNori helps coding agents deliver results that humans can actually accept.
 
-OpenNori gives coding agents a protocol surface centered on human acceptance criteria and evidence.
-The user sees whether the goal is satisfied, why, and what is still missing. The agent can still
-plan internally, but progress is determined by acceptance evidence.
+You describe a goal and constraints in natural language. Nori turns that into a Nori Contract:
+human-centered acceptance checks, evidence, and a completion report. The agent can still plan
+internally, but OpenNori treats progress as proven only when the acceptance checks have reviewable
+evidence.
 
-## Shape
+## Why It Exists
+
+AI agents often do a lot of work while leaving the user unsure whether the original goal is done.
+OpenNori keeps the conversation centered on:
+
+- what the user wants to achieve
+- what the user can open, run, see, or judge
+- what evidence supports each acceptance check
+- what is still blocked or missing
+- whether the goal is complete
+
+OpenNori is not a phase system, task planner, or process archive. It borrows productization ideas
+from mature agent workflow kits, but the main storyline stays acceptance, evidence, and completion
+judgment.
+
+## Try It
+
+```bash
+npx opennori
+```
+
+For a project install:
+
+```bash
+npm install -D opennori
+npx opennori
+```
+
+Then talk to your agent:
+
+```text
+Use OpenNori for this project. Start from my goal, define a Nori Contract,
+and keep working only from acceptance gaps until the report says whether it is complete.
+```
+
+## What Gets Added
+
+OpenNori uses one project-local state directory:
 
 ```text
 .opennori/
@@ -21,55 +59,37 @@ plan internally, but progress is determined by acceptance evidence.
   brainstorms/
 ```
 
-## Quick Start
+It does not create a `process/` directory as the main workflow surface.
+
+## Core Commands
 
 ```bash
-node ./bin/nori.js install --root . --dry-run --json
-node ./bin/nori.js install --root . --skill --json
-node ./bin/nori.js doctor --root . --json
-node ./bin/nori.js skill export --pack --json
-node ./bin/nori.js brainstorm --idea "Explore a fuzzy goal before acceptance" --root . --json
-node ./bin/nori.js draft --from-brainstorm explore-a-fuzzy-goal-before-acceptance --candidate A --root . --json
-node ./bin/nori.js draft --goal "Ship a user-visible task" --root . --json
-node ./bin/nori.js approve --root . --summary "User approved acceptance criteria." --json
-node ./bin/nori.js init examples/opennori-self.json --root . --json
-node ./bin/nori.js resume --root . --json
-node ./bin/nori.js next --root . --json
-node ./bin/nori.js status --root . --json
-node ./bin/nori.js criterion update --root . --criterion AC-P-1 --user-story "作为用户，我能判断当前验收缺口。" --json
-node ./bin/nori.js evidence add --root . --criterion AC-P-1 --kind test-summary --summary "User can inspect the Nori Contract." --result passing --basis tool-observation --source '{"type":"command","label":"npm test","command":"npm test","outcome":"passed"}' --reviewability "User can rerun the command." --limitations "Does not prove visual UX." --json
-node ./bin/nori.js profile add --root . --type skill --name design-taste-frontend --strength must --purpose "Use this Skill for the design read and theme token pass." --install-policy existing_only --json
-node ./bin/nori.js profile add --root . --type stack --name radix-ui --strength prefer --purpose "Use accessible primitives for custom components." --install-policy ask_before_install --json
-node ./bin/nori.js profile show --root . --json
-node ./bin/nori.js profile evidence --root . --item skill-design-taste-frontend --result satisfied --summary "Agent used the required Skill before implementation." --json
-node ./bin/nori.js evaluate --root . --json
-node ./bin/nori.js report --root . --json
+opennori bootstrap
+opennori doctor --root .
+opennori brainstorm --idea "Explore this goal" --root .
+opennori draft --goal "Ship a user-visible result" --root .
+opennori approve --root . --summary "User approved the acceptance checks."
+opennori status --root .
+opennori evidence add --root . --criterion AC-1 --kind review-result --summary "..." --result passing
+opennori report --root .
 ```
 
-`nori install` writes `.opennori/manifest.json` with the OpenNori version, managed files, active goals,
-optional project Skill Pack state, and supported protocol capabilities. `nori doctor` reports whether a
-project is `ready`, `needs-action`, or `broken`, with recovery actions for missing structure, stale
-manifest data, broken active goals, and stale Skills.
-
-`nori install --dry-run` returns an `install_plan` that shows each planned action, asset kind,
-managed status, write intent, destructive overwrite flag, and reason. Dry-run plans report
-`will_write: 0` so users can review install impact before applying it.
-
-Real `nori install --force` requires `--confirm`. Preview destructive actions with
-`nori install --force --dry-run --json` before applying a confirmed overwrite.
-
-`nori uninstall --dry-run --json` previews removals. Default uninstall removes entry assets while
-preserving active goals, evidence, reports, archives, and brainstorms; deleting `.opennori` state
-requires `nori uninstall --include-state --confirm --json`.
+Users should not need to memorize these commands. The OpenNori Skill Pack lets an agent map natural
+language requests to the deterministic CLI state layer.
 
-Evidence is intentionally open-ended. Agents can use tests, diffs, screenshots, logs, artifacts,
-URLs, human confirmation, AW doctor, or any other useful signal. OpenNori only requires the submitted
-evidence to be reviewable by the user: include a basis, one or more sources, reviewability,
-confidence, and limitations when the evidence affects completion.
+## Productized Boundaries
 
-`nori install --skill` installs the OpenNori Skill Pack under `.agents/skills/`: the root `nori` router
-plus focused Skills for acceptance, evidence, Nori Profile, project health, and reporting.
-Users keep using natural language; the Skills route agent behavior to the right CLI loop.
+- `bootstrap` gives agents one short entry for readiness checks and first-time preview. Lower-level
+  `install`, `upgrade`, and `uninstall` still support preview-first workflows; destructive writes
+  require explicit confirmation.
+- `doctor` reports whether project state is `ready`, `needs-action`, or `broken`, with recovery
+  actions.
+- Nori Profile records required Skills, preferred stacks, avoided tools, and install policy without
+  turning those preferences into user acceptance checks.
+- Evidence stays flexible: tests, screenshots, URLs, artifacts, logs, human confirmation, waivers, or
+  other reviewable sources can support an acceptance check.
+- Context export can give review tools the current goal, checks, profile, evidence, and report, but
+  review tools do not take over the agent loop.
 
 ## Development
 

package/bin/{nori.js → opennori.js}

@@ -1,7 +1,10 @@
 #!/usr/bin/env node
 import { main } from "../src/cli.js";
 
-main(process.argv.slice(2)).catch((error) => {
+const args = process.argv.slice(2);
+const commandArgs = args.length > 0 ? args : ["bootstrap"];
+
+main(commandArgs).catch((error) => {
   console.error(JSON.stringify({
     ok: false,
     error: {

package/examples/opennori-self.json

@@ -17,16 +17,16 @@
     {
       "id": "AC-P-2",
       "layer": "protocol",
-      "user_story": "作为用户，我运行 nori check 后，能知道验收标准是否仍然是用户视角，而不是技术实现清单。",
-      "measurement": "对当前 active goal 或故意写坏的验收草案运行 nori check。",
+      "user_story": "作为用户，我运行 opennori check 后，能知道验收标准是否仍然是用户视角，而不是技术实现清单。",
+      "measurement": "对当前 active goal 或故意写坏的验收草案运行 opennori check。",
       "threshold": "“存在文件、字段、命令、测试通过、实现某模块”这类内容不能作为用户验收标准通过校验。",
       "risk": "medium"
     },
     {
       "id": "AC-P-3",
       "layer": "protocol",
-      "user_story": "作为用户，我运行 nori next 或 nori status 后，看到的是当前验收缺口和完成判断，而不是任务步骤列表。",
-      "measurement": "运行 nori next/status 并查看返回的 current_gap、completion 和 intervention。",
+      "user_story": "作为用户，我运行 opennori next 或 opennori status 后，看到的是当前验收缺口和完成判断，而不是任务步骤列表。",
+      "measurement": "运行 opennori next/status 并查看返回的 current_gap、completion 和 intervention。",
       "threshold": "输出默认回答“当前差哪条 AC、是否完成、是否需要人类动作”，不把过程任务当作主线。",
       "risk": "medium"
     },
@@ -41,8 +41,8 @@
     {
       "id": "AC-P-5",
       "layer": "protocol",
-      "user_story": "作为用户，我运行 nori report 后，能看到目标、分层 AC 状态、证据摘要、当前缺口、是否需要我介入和结论。",
-      "measurement": "运行 nori report 或让 Codex 生成 OpenNori 报告。",
+      "user_story": "作为用户，我运行 opennori report 后，能看到目标、分层 AC 状态、证据摘要、当前缺口、是否需要我介入和结论。",
+      "measurement": "运行 opennori report 或让 Codex 生成 OpenNori 报告。",
       "threshold": "报告默认围绕验收状态和证据组织，不把过程任务当作主线。",
       "risk": "medium"
     },
@@ -50,7 +50,7 @@
       "id": "AC-P-6",
       "layer": "protocol",
       "user_story": "作为用户，我查看 OpenNori 报告时，能知道每条通过、阻塞或豁免的 AC 是基于什么证据判断的。",
-      "measurement": "给 AC 添加不同来源的证据后运行 nori report 或 nori status。",
+      "measurement": "给 AC 添加不同来源的证据后运行 opennori report 或 opennori status。",
       "threshold": "报告或状态输出展示证据摘要、判断基础、证据强度和剩余限制；不会只显示 agent 自我结论。",
       "risk": "high"
     },
@@ -97,16 +97,16 @@
     {
       "id": "AC-P-12",
       "layer": "protocol",
-      "user_story": "作为用户，我运行 nori check 后，能发现 AC 是否缺少真实用户操作或可观察结果，而不是只检查是否以“作为用户”开头。",
-      "measurement": "对包含“测试通过”“字段存在”等内部完成条件的验收草案运行 nori check，再对包含真实用户操作和报告结果的草案运行 nori check。",
+      "user_story": "作为用户，我运行 opennori check 后，能发现 AC 是否缺少真实用户操作或可观察结果，而不是只检查是否以“作为用户”开头。",
+      "measurement": "对包含“测试通过”“字段存在”等内部完成条件的验收草案运行 opennori check，再对包含真实用户操作和报告结果的草案运行 opennori check。",
       "threshold": "内部完成条件会被拒绝；包含用户运行、打开、查看、确认等操作，并说明用户能看到或判断什么结果的 AC 可以通过。",
       "risk": "high"
     },
     {
       "id": "AC-P-13",
       "layer": "protocol",
-      "user_story": "作为用户，我打开 nori report 后，能先看到完成结论、当前缺口和是否需要我介入，再查看详细 AC 表格。",
-      "measurement": "运行 nori report 并阅读报告顶部内容，再向下查看 Acceptance Status 表格。",
+      "user_story": "作为用户，我打开 opennori report 后，能先看到完成结论、当前缺口和是否需要我介入，再查看详细 AC 表格。",
+      "measurement": "运行 opennori report 并阅读报告顶部内容，再向下查看 Acceptance Status 表格。",
       "threshold": "报告在详细表格前显示 Decision Summary，包含 completion、current gap、user intervention 和 workflow status；blocked 报告也先显示需要用户采取的动作。",
       "risk": "medium"
     },
@@ -177,15 +177,15 @@
     {
       "id": "AC-Z-1",
       "layer": "productization",
-      "user_story": "作为用户，我运行 nori skill export 后，能得到可放入 Codex Skills 的 OpenNori 使用说明。",
-      "measurement": "运行 nori skill export --json 并查看输出内容。",
+      "user_story": "作为用户，我运行 opennori skill export 后，能得到可放入 Codex Skills 的 OpenNori 使用说明。",
+      "measurement": "运行 opennori skill export --json 并查看输出内容。",
       "threshold": "输出说明能指导 agent 使用 resume、next、evidence、evaluate、status 和 report，不要求用户追踪过程任务。",
       "risk": "medium"
     },
     {
       "id": "AC-Z-2",
       "layer": "productization",
-      "user_story": "作为用户，我运行 nori install 后，能把 OpenNori 放入当前项目的可用入口，并且不会意外覆盖已有内容。",
+      "user_story": "作为用户，我运行 opennori install 后，能把 OpenNori 放入当前项目的可用入口，并且不会意外覆盖已有内容。",
       "measurement": "在一个已有项目中运行安装入口并查看安装结果。",
       "threshold": "安装前能看到将创建或跳过的入口；已有内容默认不被覆盖；失败时说明用户需要做什么。",
       "risk": "high"
@@ -201,8 +201,8 @@
     {
       "id": "AC-Z-4",
       "layer": "productization",
-      "user_story": "作为用户，我运行 nori list 后，能看到多个 active goals，并能明确选择要继续的目标。",
-      "measurement": "创建多个 active goals 后运行 nori list，并用 --goal 指定 resume/status/report 的目标。",
+      "user_story": "作为用户，我运行 opennori list 后，能看到多个 active goals，并能明确选择要继续的目标。",
+      "measurement": "创建多个 active goals 后运行 opennori list，并用 --goal 指定 resume/status/report 的目标。",
       "threshold": "多个目标不会被 agent 随机选择；用户能看见目标列表、状态、当前缺口和对应路径。",
       "risk": "high"
     },
@@ -210,7 +210,7 @@
       "id": "AC-Z-5",
       "layer": "productization",
       "user_story": "作为用户，我运行归档入口后，completed 或 blocked 中保留报告，active 中不再出现这个目标。",
-      "measurement": "对 complete 或 blocked goal 执行归档，再运行 nori list 并打开归档产物。",
+      "measurement": "对 complete 或 blocked goal 执行归档，再运行 opennori list 并打开归档产物。",
       "threshold": "归档不会丢失 Nori Contract、evidence record 或 report；active 列表只显示仍需推进的目标。",
       "risk": "high"
     },
@@ -218,23 +218,23 @@
       "id": "AC-Z-6",
       "layer": "productization",
       "user_story": "作为用户，我在项目目录运行 OpenNori 后，能看到 OpenNori 状态集中在 .opennori 目录里，而不是散落到通用 process 目录。",
-      "measurement": "运行 nori install、draft、brainstorm、report 或 archive 后查看项目目录。",
+      "measurement": "运行 opennori install、draft、brainstorm、report 或 archive 后查看项目目录。",
       "threshold": "OpenNori 默认只把协议、active goal、报告、归档和 brainstorm 写入 .opennori；不创建 process/acceptance 或 process/development-protocols。",
       "risk": "medium"
     },
     {
       "id": "AC-Z-7",
       "layer": "productization",
-      "user_story": "作为用户，我运行 nori install 后，能看到当前项目的 OpenNori 接入登记信息，并判断版本、托管入口、active goals 和 Skill 状态是否可信。",
-      "measurement": "运行 nori install --dry-run 或 nori install 后查看输出和项目中的接入登记。",
+      "user_story": "作为用户，我运行 opennori install 后，能看到当前项目的 OpenNori 接入登记信息，并判断版本、托管入口、active goals 和 Skill 状态是否可信。",
+      "measurement": "运行 opennori install --dry-run 或 opennori install 后查看输出和项目中的接入登记。",
       "threshold": "输出包含 create、skip、overwrite 或 update 语义；接入登记说明 OpenNori 版本、managed files、active goals、Skill 状态和协议能力；已有用户内容默认不被覆盖。",
       "risk": "high"
     },
     {
       "id": "AC-Z-8",
       "layer": "productization",
-      "user_story": "作为用户，我运行 nori doctor 后，能判断当前项目是 ready、needs-action 还是 broken，并知道下一步修复动作。",
-      "measurement": "在已安装项目、缺少接入登记的项目或 active goal 异常的项目中运行 nori doctor。",
+      "user_story": "作为用户，我运行 opennori doctor 后，能判断当前项目是 ready、needs-action 还是 broken，并知道下一步修复动作。",
+      "measurement": "在已安装项目、缺少接入登记的项目或 active goal 异常的项目中运行 opennori doctor。",
       "threshold": "输出包含整体健康状态、逐项检查结果、active goal 可恢复性、Skill 同步状态和可执行的 recovery 建议。",
       "risk": "high"
     },
@@ -242,7 +242,7 @@
       "id": "AC-Z-9",
       "layer": "productization",
       "user_story": "作为用户，我预览 OpenNori 安装时，能判断每个项目入口会被创建、跳过、更新还是覆盖，并确认 dry-run 不会写入项目。",
-      "measurement": "运行 nori install --dry-run，查看 install plan，再检查项目文件是否未被写入。",
+      "measurement": "运行 opennori install --dry-run，查看 install plan，再检查项目文件是否未被写入。",
       "threshold": "install plan 对每个入口显示 action、kind、managed、would_write、will_write、destructive 和 reason；dry-run 下 will_write 为 0；覆盖类动作必须被标记为 destructive。",
       "risk": "high"
     },
@@ -250,7 +250,7 @@
       "id": "AC-Z-10",
       "layer": "productization",
       "user_story": "作为用户，我执行可能覆盖已有 OpenNori 入口的安装时，必须先看到预览并显式确认，才能真正写入项目。",
-      "measurement": "在已有 OpenNori 入口的项目中运行 nori install --force、nori install --force --dry-run 和确认后的安装。",
+      "measurement": "在已有 OpenNori 入口的项目中运行 opennori install --force、opennori install --force --dry-run 和确认后的安装。",
       "threshold": "未确认的真实 --force 安装会失败并提示先 dry-run；dry-run 可展示 destructive overwrite；只有带显式确认的 --force 才会执行覆盖写入。",
       "risk": "high"
     },
@@ -258,7 +258,7 @@
       "id": "AC-Z-11",
       "layer": "productization",
       "user_story": "作为用户，我卸载 OpenNori 前，能预览将移除什么，并确认默认卸载不会丢失 active goals、证据、报告或归档。",
-      "measurement": "在已安装且有 active goal 的项目中运行 nori uninstall --dry-run、未确认 uninstall、确认 uninstall 和 include-state uninstall。",
+      "measurement": "在已安装且有 active goal 的项目中运行 opennori uninstall --dry-run、未确认 uninstall、确认 uninstall 和 include-state uninstall。",
       "threshold": "默认 uninstall plan 标明 entry assets 会被移除、验收状态会被 preserve；未确认真实卸载会失败；确认后只移除入口资产；只有显式 --include-state --confirm 才会删除 .opennori 状态目录。",
       "risk": "high"
     },
@@ -266,15 +266,15 @@
       "id": "AC-Z-12",
       "layer": "productization",
       "user_story": "作为用户，我安装 OpenNori 后，agent 能获得一组职责清晰的 OpenNori Skills 来处理验收、证据、能力偏好、项目健康和报告，而我不需要记住这些 Skill 名。",
-      "measurement": "运行 nori skill export --pack、nori install --skill 和 nori doctor，查看 Skill Pack、manifest 和 doctor 结果。",
+      "measurement": "运行 opennori skill export --pack、opennori install --skill 和 opennori doctor，查看 Skill Pack、manifest 和 doctor 结果。",
       "threshold": "Skill Pack 包含总入口和 acceptance、evidence、capability-profile、project-health、reporting 子 Skill；install 会写入这些 Skill；manifest 记录 skill_pack；doctor 能发现缺失或不同步的 Skill。",
       "risk": "high"
     },
     {
       "id": "AC-Z-13",
       "layer": "productization",
-      "user_story": "作为用户，我运行 nori doctor 后，如果项目状态不健康，能直接看到一组可执行恢复动作。",
-      "measurement": "分别制造缺失 Skill Pack、缺失 manifest、stale manifest 和损坏 active goal 的项目，然后运行 nori doctor。",
+      "user_story": "作为用户，我运行 opennori doctor 后，如果项目状态不健康，能直接看到一组可执行恢复动作。",
+      "measurement": "分别制造缺失 Skill Pack、缺失 manifest、stale manifest 和损坏 active goal 的项目，然后运行 opennori doctor。",
       "threshold": "doctor 输出 status、失败 check、active_goal_issues 和 recovery_actions；recovery_actions 说明要运行的 OpenNori 命令或要检查的 .opennori/active 文件位置。",
       "risk": "high"
     },
@@ -282,7 +282,7 @@
       "id": "AC-Z-14",
       "layer": "productization",
       "user_story": "作为用户，我让 agent 继续 OpenNori 工作时，不需要每轮都追问下一步是什么。",
-      "measurement": "运行 nori resume、nori status、nori next 和 nori report，分别查看未完成、阻塞和已完成 goal 的输出。",
+      "measurement": "运行 opennori resume、opennori status、opennori next 和 opennori report，分别查看未完成、阻塞和已完成 goal 的输出。",
       "threshold": "输出包含 next_recommendation 或顶部推荐动作；未完成时指向当前验收缺口，阻塞时指向需要用户介入的事项，完成时提示 agent 可进入下一轮 OpenNori loop。",
       "risk": "high"
     },
@@ -290,16 +290,24 @@
       "id": "AC-Z-15",
       "layer": "productization",
       "user_story": "作为用户，我让 agent 记录验收证据时，不需要 agent 为常见来源手写复杂结构。",
-      "measurement": "运行 nori evidence add，分别使用 --source-command、--source-path、--source-url 和自由 --source 记录证据，再查看 status/report。",
+      "measurement": "运行 opennori evidence add，分别使用 --source-command、--source-path、--source-url 和自由 --source 记录证据，再查看 status/report。",
       "threshold": "证据来源能显示为 command、artifact、url 或自由 reference；report/status 中仍保留 basis、reviewability、limitations 和 confidence。",
       "risk": "medium"
     },
     {
       "id": "AC-Z-16",
       "layer": "productization",
-      "user_story": "作为用户，我通过 npm 获取 OpenNori 后，能使用 nori 入口初始化项目、查看帮助和运行健康检查，而不需要理解迁移历史。",
-      "measurement": "在全新临时项目中安装 opennori 包，运行 npx nori --help、npx nori install --root . --dry-run、npx nori install --root . --confirm 和 npx nori doctor --root .。",
-      "threshold": "npm registry 显示 opennori@0.1.1 且 bin.nori 指向 bin/nori.js；全新项目安装后 npx nori 可用；dry-run 只预览 .opennori 写入；真实 install 后 doctor 为 ready；项目状态只出现 OpenNori 目录。",
+      "user_story": "作为用户，我通过 npm 获取 OpenNori 后，能用 npx opennori 这个短入口开始，而不需要理解 install、root、dry-run 或 Skill Pack 参数。",
+      "measurement": "在全新临时项目中运行 npx opennori 或本地等价 opennori bin，再确认 bootstrap 后运行 opennori doctor。",
+      "threshold": "npm 包只提供 opennori 这个 bin；短入口默认只返回首次接入 preview 且不写入项目；显式确认后才创建 .opennori 和项目 Skill Pack；doctor 为 ready。",
+      "risk": "high"
+    },
+    {
+      "id": "AC-Z-17",
+      "layer": "productization",
+      "user_story": "作为用户，我第一次打开 README 或官网 Quick Start 时，能看到短到可以直接复制的 npx opennori 入口，而不是一串内部安装参数。",
+      "measurement": "阅读 README Try It 和官网首屏 Quick Start / Start 区域。",
+      "threshold": "README 和官网第一眼 Quick Start 展示 npx opennori；更详细的 opennori bootstrap、install、dry-run、confirm 只作为 agent 或高级用户的底层安全路径出现。",
       "risk": "high"
     }
   ]

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "opennori",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "OpenNori: human-centered Nori Contracts and evidence records for coding agents.",
   "type": "module",
   "bin": {
-    "nori": "bin/nori.js"
+    "opennori": "bin/opennori.js"
   },
   "files": [
     ".opennori/protocol.md",
@@ -16,7 +16,7 @@
   ],
   "scripts": {
     "test": "node --test",
-    "check": "node --test && node ./bin/nori.js doctor --json"
+    "check": "node --test && node ./bin/opennori.js doctor --json"
   },
   "publishConfig": {
     "access": "public"

package/src/cli.js

@@ -41,6 +41,7 @@ const NORI_CAPABILITIES = [
   "capability-profile",
   "profile-check",
   "archive",
+  "bootstrap",
   "report",
   "doctor",
   "upgrade",
@@ -384,7 +385,8 @@ function hasFlag(args, name) {
   return args.includes(name);
 }
 
-const TOP_LEVEL_USAGE = "nori <doctor|install|upgrade|uninstall|brainstorm|draft|init|list|check|approve|criterion|profile|resume|next|evidence|evaluate|status|report|context|changes|archive|skill>";
+const CLI_NAME = "opennori";
+const TOP_LEVEL_USAGE = `${CLI_NAME} <bootstrap|doctor|install|upgrade|uninstall|brainstorm|draft|init|list|check|approve|criterion|profile|resume|next|evidence|evaluate|status|report|context|changes|archive|skill>`;
 
 function wantsHelp(args) {
   return args.includes("--help") || args.includes("-h");
@@ -393,25 +395,26 @@ function wantsHelp(args) {
 function usageFor(args) {
   const [command, subcommand] = args;
   if (!command || command === "--help" || command === "-h") return TOP_LEVEL_USAGE;
-  if (command === "install") return "nori install --root <project> [--skill] [--dry-run] [--force] [--confirm] [--json]";
-  if (command === "upgrade") return "nori upgrade --root <project> [--skill] [--dry-run] [--confirm] [--json]";
-  if (command === "uninstall") return "nori uninstall --root <project> [--include-state] [--dry-run] [--confirm] [--json]";
-  if (command === "doctor") return "nori doctor --root <project> [--json]";
-  if (command === "brainstorm") return "nori brainstorm --idea \"<idea>\" --root <project> [--id <id>] [--json]";
-  if (command === "draft") return "nori draft --goal \"<goal>\" --root <project> [--goal-id <id>] [--json]";
-  if (command === "init") return "nori init <brief.json> --root <project> [--json]";
-  if (command === "criterion" && subcommand === "update") return "nori criterion update --root <project> --criterion <id> --user-story ... --measurement ... --threshold ... [--json]";
-  if (command === "profile" && subcommand === "add") return "nori profile add --root <project> --type <skill|stack|constraint> --name <name> --strength <must|prefer|avoid> --purpose <purpose> [--json]";
-  if (command === "profile" && subcommand === "evidence") return "nori profile evidence --root <project> --item <item-id> --result <satisfied|violated|waived> --summary <summary> [--json]";
-  if (command === "profile") return "nori profile <add|evidence|show|check> --root <project> [--json]";
-  if (command === "evidence" && subcommand === "add") return "nori evidence add --root <project> --criterion <id> --kind <kind> --summary <summary> --result <passing|failing|blocked|waived> [--json]";
-  if (command === "evidence") return "nori evidence add --root <project> --criterion <id> --kind <kind> --summary <summary> --result <passing|failing|blocked|waived> [--json]";
-  if (command === "context" && subcommand === "export") return "nori context export --root <project> [--json]";
-  if (command === "context") return "nori context export --root <project> [--json]";
-  if (command === "skill" && subcommand === "export") return "nori skill export [--pack] [--json]";
-  if (command === "skill") return "nori skill export [--pack] [--json]";
+  if (command === "bootstrap") return `${CLI_NAME} bootstrap --root <project> [--confirm] [--json]`;
+  if (command === "install") return `${CLI_NAME} install --root <project> [--skill] [--dry-run] [--force] [--confirm] [--json]`;
+  if (command === "upgrade") return `${CLI_NAME} upgrade --root <project> [--skill] [--dry-run] [--confirm] [--json]`;
+  if (command === "uninstall") return `${CLI_NAME} uninstall --root <project> [--include-state] [--dry-run] [--confirm] [--json]`;
+  if (command === "doctor") return `${CLI_NAME} doctor --root <project> [--json]`;
+  if (command === "brainstorm") return `${CLI_NAME} brainstorm --idea "<idea>" --root <project> [--id <id>] [--json]`;
+  if (command === "draft") return `${CLI_NAME} draft --goal "<goal>" --root <project> [--goal-id <id>] [--json]`;
+  if (command === "init") return `${CLI_NAME} init <brief.json> --root <project> [--json]`;
+  if (command === "criterion" && subcommand === "update") return `${CLI_NAME} criterion update --root <project> --criterion <id> --user-story ... --measurement ... --threshold ... [--json]`;
+  if (command === "profile" && subcommand === "add") return `${CLI_NAME} profile add --root <project> --type <skill|stack|constraint> --name <name> --strength <must|prefer|avoid> --purpose <purpose> [--json]`;
+  if (command === "profile" && subcommand === "evidence") return `${CLI_NAME} profile evidence --root <project> --item <item-id> --result <satisfied|violated|waived> --summary <summary> [--json]`;
+  if (command === "profile") return `${CLI_NAME} profile <add|evidence|show|check> --root <project> [--json]`;
+  if (command === "evidence" && subcommand === "add") return `${CLI_NAME} evidence add --root <project> --criterion <id> --kind <kind> --summary <summary> --result <passing|failing|blocked|waived> [--json]`;
+  if (command === "evidence") return `${CLI_NAME} evidence add --root <project> --criterion <id> --kind <kind> --summary <summary> --result <passing|failing|blocked|waived> [--json]`;
+  if (command === "context" && subcommand === "export") return `${CLI_NAME} context export --root <project> [--json]`;
+  if (command === "context") return `${CLI_NAME} context export --root <project> [--json]`;
+  if (command === "skill" && subcommand === "export") return `${CLI_NAME} skill export [--pack] [--json]`;
+  if (command === "skill") return `${CLI_NAME} skill export [--pack] [--json]`;
   if (["list", "check", "approve", "resume", "next", "evaluate", "status", "report", "changes", "archive"].includes(command)) {
-    return `nori ${command} --root <project> [--goal <goal-id>] [--json]`;
+    return `${CLI_NAME} ${command} --root <project> [--goal <goal-id>] [--json]`;
   }
   return TOP_LEVEL_USAGE;
 }
@@ -477,9 +480,10 @@ const SKILL_PACK = [
       "- Status, report, current gap, completion answer, user intervention, or change summary -> use `nori-reporting`.",
       "",
       "## Baseline",
-      "At the start of each OpenNori turn, run `nori resume --root <repo> --json` or `nori status --root <repo> --json` unless the task is only install/doctor/uninstall.",
+      "At the start of each OpenNori turn, run `opennori bootstrap --root <repo> --json` if project readiness is unknown; otherwise run `opennori resume --root <repo> --json` or `opennori status --root <repo> --json`.",
+      "If bootstrap returns `needs_confirm`, show the preview briefly and ask the user before rerunning with `--confirm`.",
       "Use `next_recommendation` and top-level `next_actions` to continue the OpenNori loop; do not make the user repeatedly ask what the next step is.",
-      "If `nori` is not on PATH, use the installed package binary such as `node ./node_modules/opennori/bin/nori.js` or this repository's `node ./bin/nori.js` with the same arguments.",
+      "If `opennori` is not on PATH, use the installed package binary such as `node ./node_modules/opennori/bin/opennori.js` or this repository's `node ./bin/opennori.js` with the same arguments.",
       "",
       "## Rule",
       "Progress is determined by acceptance evidence, not implementation steps.",
@@ -495,11 +499,11 @@ const SKILL_PACK = [
       "Use when the user gives a goal, wants to brainstorm acceptance directions, approves criteria, revises completion criteria, or says the AC is wrong.",
       "",
       "## Commands",
-      "- Fuzzy idea or discussion: `nori brainstorm --idea \"<idea>\" --root <repo> --json`.",
-      "- Start from a goal: `nori draft --goal \"<goal>\" --root <repo> --json`.",
-      "- Start from a chosen brainstorm candidate: `nori draft --from-brainstorm <brainstorm-id> --candidate <A|B|C> --root <repo> --json`.",
-      "- User approves criteria: `nori approve --root <repo> --summary \"<approval>\" --json`.",
-      "- User revises a criterion: `nori criterion update --root <repo> --criterion <id> --user-story ... --measurement ... --threshold ... --json`.",
+      "- Fuzzy idea or discussion: `opennori brainstorm --idea \"<idea>\" --root <repo> --json`.",
+      "- Start from a goal: `opennori draft --goal \"<goal>\" --root <repo> --json`.",
+      "- Start from a chosen brainstorm candidate: `opennori draft --from-brainstorm <brainstorm-id> --candidate <A|B|C> --root <repo> --json`.",
+      "- User approves criteria: `opennori approve --root <repo> --summary \"<approval>\" --json`.",
+      "- User revises a criterion: `opennori criterion update --root <repo> --criterion <id> --user-story ... --measurement ... --threshold ... --json`.",
       "",
       "## Rules",
       "ACs must describe user actions or judgments, not implementation files, commands, modules, fields, tests, Skills, or technology choices.",
@@ -519,7 +523,7 @@ const SKILL_PACK = [
       "When submitting evidence, explain basis, sources, reviewability, confidence, and limitations.",
       "",
       "## Command",
-      "`nori evidence add --root <repo> --criterion <id> --kind <kind> --summary \"...\" --result <passing|failing|blocked|waived> --basis <basis> --source '<json-or-label>' --source-command '<command>' --source-path '<path>' --source-url '<url>' --reviewability \"...\" --limitations \"...\" --json`",
+      "`opennori evidence add --root <repo> --criterion <id> --kind <kind> --summary \"...\" --result <passing|failing|blocked|waived> --basis <basis> --source '<json-or-label>' --source-command '<command>' --source-path '<path>' --source-url '<url>' --reviewability \"...\" --limitations \"...\" --json`",
       "",
       "Use multiple source flags when one AC is supported by several signals; prefer typed `--source-command`, `--source-path`, or `--source-url` when they fit, and use raw `--source` for anything else.",
       "For high-risk passing evidence, use a strong evidence kind or explicit strong confidence only when justified.",
@@ -534,9 +538,9 @@ const SKILL_PACK = [
       "Use when the user says a task must use a Skill, prefers a technology stack, wants to avoid a tool/library, or requires asking before installs.",
       "",
       "## Commands",
-      "- Add preference: `nori profile add --root <repo> --type <skill|stack|constraint> --name \"<name>\" --strength <must|prefer|avoid> --purpose \"<why>\" --install-policy <existing_only|ask_before_install|allowed> --json`.",
-      "- Add compliance evidence: `nori profile evidence --root <repo> --item <item-id> --result <satisfied|violated|waived> --summary \"<evidence>\" --json`.",
-      "- Show profile: `nori profile show --root <repo> --json`.",
+      "- Add preference: `opennori profile add --root <repo> --type <skill|stack|constraint> --name \"<name>\" --strength <must|prefer|avoid> --purpose \"<why>\" --install-policy <existing_only|ask_before_install|allowed> --json`.",
+      "- Add compliance evidence: `opennori profile evidence --root <repo> --item <item-id> --result <satisfied|violated|waived> --summary \"<evidence>\" --json`.",
+      "- Show profile: `opennori profile show --root <repo> --json`.",
       "",
       "## Rules",
       "Do not turn Skills or stack preferences into user ACs.",
@@ -552,14 +556,16 @@ const SKILL_PACK = [
       "Use when the user asks to install OpenNori, uninstall OpenNori, check whether OpenNori is ready, diagnose broken OpenNori state, inspect manifest, or sync project Skills.",
       "",
       "## Commands",
-      "- Preview install: `nori install --root <repo> --dry-run --json`.",
-      "- Install Skill Pack: `nori install --root <repo> --skill --json`.",
-      "- Preview destructive install: `nori install --root <repo> --skill --force --dry-run --json`.",
-      "- Confirm destructive install: `nori install --root <repo> --skill --force --confirm --json`.",
-      "- Doctor: `nori doctor --root <repo> --json`.",
-      "- Preview uninstall: `nori uninstall --root <repo> --dry-run --json`.",
-      "- Remove entry assets while preserving state: `nori uninstall --root <repo> --confirm --json`.",
-      "- Remove all OpenNori state only after explicit user acceptance: `nori uninstall --root <repo> --include-state --confirm --json`.",
+      "- Short readiness / first-time preview: `opennori bootstrap --root <repo> --json`.",
+      "- Confirm first-time setup after user approval: `opennori bootstrap --root <repo> --confirm --json`.",
+      "- Preview install: `opennori install --root <repo> --dry-run --json`.",
+      "- Install Skill Pack: `opennori install --root <repo> --skill --json`.",
+      "- Preview destructive install: `opennori install --root <repo> --skill --force --dry-run --json`.",
+      "- Confirm destructive install: `opennori install --root <repo> --skill --force --confirm --json`.",
+      "- Doctor: `opennori doctor --root <repo> --json`.",
+      "- Preview uninstall: `opennori uninstall --root <repo> --dry-run --json`.",
+      "- Remove entry assets while preserving state: `opennori uninstall --root <repo> --confirm --json`.",
+      "- Remove all OpenNori state only after explicit user acceptance: `opennori uninstall --root <repo> --include-state --confirm --json`.",
       "",
       "## Rules",
       "Always show dry-run plans before destructive writes.",
@@ -574,12 +580,12 @@ const SKILL_PACK = [
       "Use when the user asks whether work is complete, what remains, what they need to do, what changed, or asks for an OpenNori report.",
       "",
       "## Commands",
-      "- Resume: `nori resume --root <repo> --json`.",
-      "- Next gap: `nori next --root <repo> --json`.",
-      "- Status: `nori status --root <repo> --json`.",
-      "- Report: `nori report --root <repo> --json`.",
-      "- Changes: `nori changes --root <repo> --json`.",
-      "- List goals: `nori list --root <repo> --json`.",
+      "- Resume: `opennori resume --root <repo> --json`.",
+      "- Next gap: `opennori next --root <repo> --json`.",
+      "- Status: `opennori status --root <repo> --json`.",
+      "- Report: `opennori report --root <repo> --json`.",
+      "- Changes: `opennori changes --root <repo> --json`.",
+      "- List goals: `opennori list --root <repo> --json`.",
       "",
       "## Rules",
       "Lead with completion state, current gap, evidence basis, and required human intervention.",
@@ -732,7 +738,7 @@ function protocolTemplate() {
     "",
     "Progress is determined by human-centered acceptance evidence, not by implementation steps.",
     "",
-    "Use `nori init`, `nori resume`, `nori next`, `nori evidence add`, `nori evaluate`, `nori status`, and `nori report`.",
+    "Use `opennori init`, `opennori resume`, `opennori next`, `opennori evidence add`, `opennori evaluate`, `opennori status`, and `opennori report`.",
     ""
   ].join("\n");
 }
@@ -1084,7 +1090,7 @@ function doctor(root) {
     "opennori_directory",
     fs.existsSync(noriDir),
     fs.existsSync(noriDir) ? ".opennori directory exists." : ".opennori directory is missing.",
-    "Run nori install --root <project> --json."
+    "Run opennori bootstrap --root <project> --json."
   ));
 
   for (const dir of REQUIRED_NORI_DIRS) {
@@ -1093,7 +1099,7 @@ function doctor(root) {
       `dir_${dir}`,
       fs.existsSync(dirPath),
       fs.existsSync(dirPath) ? `.opennori/${dir} exists.` : `.opennori/${dir} is missing.`,
-      "Run nori install --root <project> --json."
+      "Run opennori bootstrap --root <project> --json."
     ));
   }
 
@@ -1101,7 +1107,7 @@ function doctor(root) {
     "protocol_file",
     fs.existsSync(protocolPath),
     fs.existsSync(protocolPath) ? ".opennori/protocol.md exists." : ".opennori/protocol.md is missing.",
-    "Run nori install --root <project> --json."
+    "Run opennori bootstrap --root <project> --json."
   ));
 
   let manifest = null;
@@ -1114,7 +1120,7 @@ function doctor(root) {
       "manifest_file",
       false,
       fs.existsSync(manifestFile) ? `.opennori/manifest.json is unreadable: ${error.message}` : ".opennori/manifest.json is missing.",
-      "Run nori install --root <project> --json to create or refresh the OpenNori manifest.",
+      "Run opennori bootstrap --root <project> --json to preview setup or refresh the OpenNori manifest.",
       fs.existsSync(manifestFile) ? "broken" : "needs-action"
     ));
   }
@@ -1124,27 +1130,27 @@ function doctor(root) {
       "manifest_file",
       manifest.schema_version === MANIFEST_SCHEMA_VERSION,
       `.opennori/manifest.json uses schema ${manifest.schema_version || "<missing>"}.`,
-      "Refresh the manifest with nori install --root <project> --json.",
+      "Refresh the manifest with opennori bootstrap --root <project> --json.",
       "broken"
     ));
     checks.push(doctorCheck(
       "manifest_protocol",
       manifest.protocol_version === PROTOCOL_VERSION,
       `.opennori/manifest.json records protocol ${manifest.protocol_version || "<missing>"}.`,
-      "Refresh the manifest with nori install --root <project> --json.",
+      "Refresh the manifest with opennori bootstrap --root <project> --json.",
       "broken"
     ));
     checks.push(doctorCheck(
       "manifest_cli_version",
       manifest.opennori_version === PACKAGE_JSON.version,
       `.opennori/manifest.json records OpenNori version ${manifest.opennori_version || "<missing>"}.`,
-      "Refresh the manifest with nori install --root <project> --json."
+      "Refresh the manifest with opennori bootstrap --root <project> --json."
     ));
     checks.push(doctorCheck(
       "manifest_capabilities",
       sameStringSet(manifest.capabilities, NORI_CAPABILITIES),
       Array.isArray(manifest.capabilities) ? "Manifest protocol capabilities are readable." : "Manifest protocol capabilities are missing.",
-      "Refresh the manifest with nori install --root <project> --json."
+      "Refresh the manifest with opennori bootstrap --root <project> --json."
     ));
 
     const currentGoals = new Set(active.details.filter((goal) => goal.recoverable).map((goal) => goal.goal_id));
@@ -1157,7 +1163,7 @@ function doctor(root) {
       "manifest_active_goals",
       staleGoals.length === 0,
       staleGoals.length === 0 ? "Manifest active goals match recoverable active goals." : `Manifest active goals differ: ${staleGoals.join(", ")}.`,
-      "Run any OpenNori state-changing command, or run nori install --root <project> --json, to refresh the manifest."
+      "Run any OpenNori state-changing command, or run opennori bootstrap --root <project> --json, to refresh the manifest."
     ));
 
     const missingManaged = (manifest.managed_files || [])
@@ -1168,7 +1174,7 @@ function doctor(root) {
       "managed_files",
       missingManaged.length === 0,
       missingManaged.length === 0 ? "Required OpenNori managed files are present." : `Missing managed files: ${missingManaged.join(", ")}.`,
-      "Run nori install --root <project> --json."
+      "Run opennori bootstrap --root <project> --json."
     ));
   }
 
@@ -1176,7 +1182,7 @@ function doctor(root) {
     "active_goals_recoverable",
     active.issues.length === 0,
     active.issues.length === 0 ? `${active.details.length} active goal(s) are recoverable.` : `${active.issues.length} active goal issue(s) found.`,
-    "Inspect active_goal_issues, fix the reported .opennori/active/<goal>.acceptance.md and .opennori/active/<goal>.evidence.json pair, then rerun nori doctor --root <project> --json.",
+    "Inspect active_goal_issues, fix the reported .opennori/active/<goal>.acceptance.md and .opennori/active/<goal>.evidence.json pair, then rerun opennori doctor --root <project> --json.",
     "broken"
   ));
 
@@ -1189,7 +1195,7 @@ function doctor(root) {
       "manifest_skill_state",
       Boolean(manifest.skill) && manifest.skill.installed === skill.installed && manifest.skill.path === skill.path,
       "Manifest Skill state matches the project Skill location.",
-      "Refresh the manifest with nori install --root <project> --json."
+      "Refresh the manifest with opennori bootstrap --root <project> --json."
     ));
   }
   checks.push(doctorCheck(
@@ -1198,7 +1204,7 @@ function doctor(root) {
     skill.installed
       ? (skill.in_sync ? "Project OpenNori Skill is installed and in sync." : "Project OpenNori Skill is installed but stale.")
       : "Project OpenNori Skill is not installed; this is optional unless the manifest expects it.",
-    "Run nori install --root <project> --skill --force --json."
+    "Run opennori install --root <project> --skill --force --json."
   ));
   const manifestPackNames = new Set((manifest?.skill_pack?.skills || []).map((entry) => entry.name));
   const packNames = new Set(skillPack.skills.map((entry) => entry.name));
@@ -1210,7 +1216,7 @@ function doctor(root) {
     "skill_pack_manifest",
     manifestPackMatches,
     manifestPackMatches ? "Manifest Skill Pack state is readable." : "Manifest Skill Pack state is missing or stale.",
-    "Refresh the manifest with nori install --root <project> --skill --json."
+    "Refresh the manifest with opennori install --root <project> --skill --json."
   ));
   const packExpected = manifest?.skill_pack?.installed === true || skillPack.skills.some((entry) => entry.installed);
   const packOk = packExpected ? skillPack.installed && skillPack.in_sync : true;
@@ -1220,7 +1226,7 @@ function doctor(root) {
     skillPack.installed
       ? (skillPack.in_sync ? "OpenNori Skill Pack is installed and in sync." : "OpenNori Skill Pack is installed but stale.")
       : "OpenNori Skill Pack is not installed; this is optional unless the manifest expects it.",
-    "Run nori install --root <project> --skill --force --json."
+    "Run opennori install --root <project> --skill --force --json."
   ));
 
   const status = checks.every((check) => check.ok)
@@ -1372,6 +1378,71 @@ function refreshManifest(root) {
   }
 }
 
+function installActions(root, { dryRun = false, force = false, requestedSkill = false } = {}) {
+  const actions = [
+    ensureDir(path.join(root, ".opennori", "active"), { dryRun }),
+    ensureDir(path.join(root, ".opennori", "completed"), { dryRun }),
+    ensureDir(path.join(root, ".opennori", "blocked"), { dryRun }),
+    ensureDir(path.join(root, ".opennori", "reports"), { dryRun }),
+    ensureDir(path.join(root, ".opennori", "brainstorms"), { dryRun }),
+    writeIfSafe(path.join(root, ".opennori", "protocol.md"), protocolTemplate(), { dryRun, force, kind: "protocol" })
+  ];
+
+  if (requestedSkill) {
+    actions.push(...skillPackInstallActions(root, { dryRun, force }));
+  }
+  actions.push(writeManifest(root, { dryRun }));
+  return actions;
+}
+
+function bootstrap(root, { confirmed = false } = {}) {
+  const health = doctor(root);
+  if (health.status === "ready") {
+    return ok({
+      root,
+      status: "ready",
+      confirmed,
+      side_effect: "none",
+      doctor: health,
+      next: "OpenNori is ready. Continue from opennori resume/status, brainstorm, or draft based on the user's goal."
+    });
+  }
+
+  const hasState = fs.existsSync(path.join(root, ".opennori"));
+  const needsConfirm = !confirmed;
+  const actions = installActions(root, {
+    dryRun: needsConfirm,
+    force: false,
+    requestedSkill: true
+  });
+  const installPlan = buildInstallPlan(root, actions, {
+    dryRun: needsConfirm,
+    force: false,
+    requestedSkill: true
+  });
+  const next = needsConfirm
+    ? "Show this preview to the user and ask for confirmation before writing OpenNori project assets."
+    : "OpenNori project assets are installed. Continue with the user's goal.";
+
+  return ok(
+    {
+      root,
+      status: needsConfirm ? "needs_confirm" : "installed",
+      confirmed,
+      existing_state: hasState,
+      install_plan: installPlan,
+      actions: installPlan.actions,
+      doctor: needsConfirm ? health : doctor(root),
+      next
+    },
+    [],
+    hasState && health.status === "broken"
+      ? ["Existing OpenNori state was not ready before bootstrap; review doctor output after install."]
+      : [],
+    [next]
+  );
+}
+
 function loadPair(args) {
   const explicitAcceptance = argValue(args, "--acceptance");
   const explicitEvidence = argValue(args, "--evidence");
@@ -1423,10 +1494,17 @@ export async function main(args) {
     return;
   }
 
+  if (command === "bootstrap") {
+    const root = resolveRoot(args);
+    const confirmed = hasFlag(args, "--confirm");
+    printJson(bootstrap(root, { confirmed }));
+    return;
+  }
+
   if (command === "doctor") {
     const root = resolveRoot(args);
     printJson(ok({
-      name: "nori",
+      name: "opennori",
       root,
       ...doctor(root),
       side_effect: "none"
@@ -1460,25 +1538,13 @@ export async function main(args) {
       printJson(fail(
         "confirm_required",
         "Install --force may overwrite existing OpenNori-managed files.",
-        "Run nori install --root <project> --dry-run --force --json first, then rerun with --confirm if the destructive actions are acceptable."
+        "Run opennori install --root <project> --dry-run --force --json first, then rerun with --confirm if the destructive actions are acceptable."
       ));
       process.exitCode = 1;
       return;
     }
-    const actions = [
-      ensureDir(path.join(root, ".opennori", "active"), { dryRun }),
-      ensureDir(path.join(root, ".opennori", "completed"), { dryRun }),
-      ensureDir(path.join(root, ".opennori", "blocked"), { dryRun }),
-      ensureDir(path.join(root, ".opennori", "reports"), { dryRun }),
-      ensureDir(path.join(root, ".opennori", "brainstorms"), { dryRun }),
-      writeIfSafe(path.join(root, ".opennori", "protocol.md"), protocolTemplate(), { dryRun, force, kind: "protocol" })
-    ];
-
-    if (requestedSkill) {
-      actions.push(...skillPackInstallActions(root, { dryRun, force }));
-    }
-    const manifestAction = writeManifest(root, { dryRun });
-    actions.push(manifestAction);
+    const actions = installActions(root, { dryRun, force, requestedSkill });
+    const manifestAction = actions.find((action) => action.kind === "manifest");
     const installPlan = buildInstallPlan(root, actions, { dryRun, force, requestedSkill });
 
     printJson(ok({
@@ -1505,7 +1571,7 @@ export async function main(args) {
       printJson(fail(
         "confirm_required",
         "Uninstall removes OpenNori-managed project assets.",
-        "Run nori uninstall --root <project> --dry-run --json first, then rerun with --confirm if the planned removals are acceptable."
+        "Run opennori uninstall --root <project> --dry-run --json first, then rerun with --confirm if the planned removals are acceptable."
       ));
       process.exitCode = 1;
       return;
@@ -1538,7 +1604,7 @@ export async function main(args) {
       printJson(fail(
         "confirm_required",
         "Upgrade refreshes OpenNori manifest, protocol, and optionally Skill Pack assets.",
-        "Run nori upgrade --root <project> --dry-run --json first, then rerun with --confirm if the planned updates are acceptable."
+        "Run opennori upgrade --root <project> --dry-run --json first, then rerun with --confirm if the planned updates are acceptable."
       ));
       process.exitCode = 1;
       return;
@@ -1548,7 +1614,7 @@ export async function main(args) {
       printJson(fail(
         "install_required",
         "Upgrade found missing OpenNori entry assets.",
-        "Run nori install --root <project> --dry-run --json before upgrading missing assets."
+        "Run opennori install --root <project> --dry-run --json before upgrading missing assets."
       ));
       process.exitCode = 1;
       return;
@@ -1595,7 +1661,7 @@ export async function main(args) {
         { kind: "brainstorm_markdown", path: paths.markdownPath }
       ],
       [],
-      ["Ask the user to choose or revise a candidate before running nori draft."]
+      ["Ask the user to choose or revise a candidate before running opennori draft."]
     ));
     return;
   }
@@ -1677,7 +1743,7 @@ export async function main(args) {
         { kind: "evidence_ledger", path: paths.evidencePath }
       ],
       [],
-      ["Run nori next --acceptance <path> --evidence <path> --json before choosing implementation work."]
+      ["Run opennori next --acceptance <path> --evidence <path> --json before choosing implementation work."]
     ));
     return;
   }