agent-bios 0.19.1 → 0.19.2

package/DEPENDENCIES.md

@@ -17,33 +17,33 @@ The verification column states the scope of each check.
 
 The supported operating systems are macOS and Linux (`package.json` `os`). Private
 transactions, instruction capture and app registration use POSIX file locks, file
-descriptors and symlinks. The JSON setup protocol, machine-mode corpus operations,
+descriptors and symlinks. The JSON setup protocol, machine-mode instructions operations,
 import and app context use Python standard libraries. Interactive installation,
-package/current-checkout Corpus Studio and the private/current-checkout launcher's
+package/current-checkout Instructions Studio and the private/current-checkout launcher's
 rich entrypoint load the shipped
 offline UI dependencies. Optional learning validation and retained compatibility clients
 have separate runtime requirements below.
 
 | Tool | Required by | Required capability | Verified |
 | --- | --- | --- | --- |
-| `python3` | `compose/corpus*.py`, app bridge helper, `session-cost.py`, `launch/agent-launch.py` | Python 3.11+ (`tomllib`) for the private store, offline installer UI loader, import evidence, app receipts and native session adapter | 3.14.5 · version report · 2026-09-12 |
+| `python3` | `compose/instructions*.py`, app bridge helper, `session-cost.py`, `launch/agent-launch.py` | Python 3.11+ (`tomllib`) for the private store, offline installer UI loader, import evidence, app receipts and native session adapter | 3.14.5 · version report · 2026-09-12 |
 | `bash` | `install.sh`, shell adapters, provisioner and app helper command dispatch | Bash arrays and argument-preserving execution; macOS system Bash is supported | 3.2.57 · version report · 2026-09-12 |
 | `git` | conversation source acquisition, clone updates and version-control workflows | clone and detached checkout for a fixed source commit; worktrees and modern revision operations for development. No Git checkout is required to use an installed npm package | 2.50.1 · version report · 2026-09-12 |
 | `zsh` | `launch/agent-launch.zsh`, optional `launch/shell_integration.py` connection | shell functions, TTY checks and argument-preserving dispatch. Used by the explicit private shell connection as well as compatibility installation; it is not required for ordinary private storage or app context use | 5.9 · version report · 2026-09-12 |
 | `mktemp`, `cp` | wrapper temporary homes and shell utilities | BSD or GNU command interfaces | local inventory checks command availability; no package-version claim |
 | `ioreg`, `ps` | conversation setup machine/process identity on macOS | local OS identity probes. Linux uses machine-id and `/proc`; machine identity has a host/filesystem fallback, while missing process evidence leaves a running attempt unconfirmed | source-defined probes; no separate tool version pin |
-| Node.js | npm delivery, optional npm host installation and selected slide jobs | `package.json` requires Node >=18 for npm package delivery. The optional Claude npm recipe requires Node >=22; Codex npm installation and slide runtimes retain their own requirements. The Python corpus runtime does not require Node | 26.0.0 · version report · 2026-09-12 |
+| Node.js | npm delivery, optional npm host installation and selected slide jobs | `package.json` requires Node >=18 for npm package delivery. The optional Claude npm recipe requires Node >=22; Codex npm installation and slide runtimes retain their own requirements. The Python instructions runtime does not require Node | 26.0.0 · version report · 2026-09-12 |
 | `npm` | package delivery and optional host installation recipes | normal global package installation using the user's configured prefix/registry | 12.0.2 · version report · 2026-09-12 |
 | Homebrew (`brew`) | optional setup installation recipes | available formula/cask installation commands selected in the reviewed setup plan; setup does not install Homebrew itself | local `--version` probe; no installation version pin |
 | Python `venv`, `ensurepip` and pip | explicitly selected managed-environment installation | create an isolated environment using `AGENT_LAUNCH_PYTHON` (default `python3`); not prerequisites for loading the bundled installation UI. Some Linux Python distributions provide these components separately | clean venv creation and `pip check` · Python 3.14.5 · 2026-09-12 |
-| Bundled Textual UI runtime | interactive `install`/`onboard`, package/current-checkout Corpus Studio TTY entrypoint, private/current-checkout launcher rich entrypoint | pure-Python wheels shipped under `compose/ui_runtime/`; the loader verifies and extracts them temporarily before UI imports. No system/managed Textual, pip installation or runtime network access is needed | manifest versions/hashes/licenses; offline clean-interpreter, TTY and backend-handoff checks · 2026-09-12 |
+| Bundled Textual UI runtime | interactive `install`/`onboard`, package/current-checkout Instructions Studio TTY entrypoint, private/current-checkout launcher rich entrypoint | pure-Python wheels shipped under `compose/ui_runtime/`; the loader verifies and extracts them temporarily before UI imports. No system/managed Textual, pip installation or runtime network access is needed | manifest versions/hashes/licenses; offline clean-interpreter, TTY and backend-handoff checks · 2026-09-12 |
 | Managed `textual` | standalone compatibility launcher copies, retained in-process APIs and author tests | optional environment at `${AGENT_LAUNCH_VENV:-$HOME/.local/share/agent-launch/venv}`. Its installation target is `TEXTUAL_PIN`; current package CLI UI paths use the shipped bundle | 8.2.8 · clean-venv installation/import, `pip check` and UI tests · 2026-09-12 |
 | `rich` | Textual clients | included with the installer UI bundle and otherwise provided transitively by Textual; not a separate setup choice. Plain editing needs no optional syntax-highlighting packages | managed Textual environment and UI tests · 2026-09-12; bundled version belongs to the manifest |
 | `jsonschema` | `learn/collect-learning.py`, `learn/check-learning.py` | Draft 2020-12 validation for user learning capture and author verification. `learn` uses a usable system validator, otherwise the configured managed interpreter. Installation target is `JSONSCHEMA_PIN` in the provisioner; `--learning-only` installs it without adding Textual | 4.26.0 · clean-venv installation/import and `pip check` · 2026-09-12 |
 
 `agent-bios install` and `onboard` are interactive unless `--non-interactive` is explicit.
 Selection flags seed the UI, and a non-TTY default call fails before writes. Python
-3.11+ is still required. `compose/corpus_ui_runtime.py` validates the shipped bundle
+3.11+ is still required. `compose/instructions_ui_runtime.py` validates the shipped bundle
 before UI imports and uses one process-owned temporary extraction, cleaned on normal
 exit and released by the launcher before backend `execve`. It creates no persistent UI
 package installation. Missing, damaged or conflicting bundle state produces repair
@@ -53,8 +53,8 @@ in-process APIs retain their existing dependency contract; CLI bundle activation
 explicit at the real entrypoints.
 
 The terminal installer language chooser and its English/Korean/Japanese messages are
-owned by `compose/corpus_setup_i18n.py`. This is a per-run UI choice before dependency
-probes, not another corpus language or persisted host setting. Locale variables suggest
+owned by `compose/instructions_setup_i18n.py`. This is a per-run UI choice before dependency
+probes, not another instructions language or persisted host setting. Locale variables suggest
 a starting choice; the user still sees the chooser. The JSON setup protocol accepts an
 explicit review language while retaining its stable field names and exact values.
 
@@ -73,7 +73,7 @@ Setup probes installed commands without installing or signing in. Available depe
 actions have fixed argv and run only after explicit selection and Apply. The app bridge
 retains the configured managed-environment path for later learning calls. Host sign-in,
 user MCP credentials, browser/job bindings and personal skills remain separate setup
-steps; absence of an optional route does not make the local corpus store unavailable.
+steps; absence of an optional route does not make the local instructions store unavailable.
 Manager recipes are offered only after their version probe succeeds. Creating a new
 managed environment requires the selected Python venv/ensurepip bootstrap; an existing
 managed interpreter does not need to bootstrap again. The provisioner checks Python
@@ -84,14 +84,14 @@ managed interpreter does not need to bootstrap again. The provisioner checks Pyt
 | CLI | Required by | Required capability | Verification |
 | --- | --- | --- | --- |
 | Claude Code | native Claude sessions and Claude worker/review routes | `--model`, `--effort`, `--agents`, per-call `--append-system-prompt`, `--session-id`, `--resume`, `--mcp-config`, `--plugin-dir`, and the selected permission mode; native global/project loading remains native | 2.1.268 · 2026-09-12 |
-| Codex CLI | `compose/corpus_session.py`, launcher and Codex worker/review adapters | per-call `-c`; cwd-aware `app-server --stdio` `config/read`; durable `thread/start`, `thread/inject_items`, `thread/read`; `codex resume`; `codex exec` and agent-config projection | local 0.153.4; isolated compatibility 0.154.0 · 2026-09-12 |
+| Codex CLI | `compose/instructions_session.py`, launcher and Codex worker/review adapters | per-call `-c`; cwd-aware `app-server --stdio` `config/read`; durable `thread/start`, `thread/inject_items`, `thread/read`; `codex resume`; `codex exec` and agent-config projection | local 0.153.4; isolated compatibility 0.154.0 · 2026-09-12 |
 
 The Claude row reports the installed command version. The Codex row distinguishes the
 installed runtime from the newer isolated compatibility check. Native protocol and
 execution evidence have narrower scope:
 
 - Optional global-instruction exclusion requires Claude Code **2.1.263+**, enforced by
-  `compose/corpus_session.py`. The adapter supplies `claudeMdExcludes` through one
+  `compose/instructions_session.py`. The adapter supplies `claudeMdExcludes` through one
   `--settings` argument and refuses a conflicting existing argument. Include/exclude/
   resume startup preserving project sources was observed on 2026-09-08. The current
   Codex adapter has no supported global-only exclusion in the verified 0.154.0 protocol;
@@ -104,13 +104,13 @@ execution evidence have narrower scope:
   and `--mcp-config`; parser/projection verification used 2.1.263. Its allowed tools and
   effort choices come from the launch bindings. A parser check is not a model-generation
   receipt.
-- Native corpus hooks use the common installed Python carrier and typed event/matcher.
+- Native instructions hooks use the common installed Python carrier and typed event/matcher.
   Claude plugin delivery was exercised with 2.1.268; Codex inline hook discovery and
   local-transport execution controls used 0.153.4. Existing host hooks, enablement and
   native trust remain in force. Discovery alone does not prove execution.
 - Codex deep-review flag checks used 0.146.0. The Claude `ultracode` keyword trigger was
   read from the 2.1.220 installed bundle. These feature observations are not refreshed
-  by the current `--version` reports. Authenticated corpus-agent execution and post-fix
+  by the current `--version` reports. Authenticated instructions-agent execution and post-fix
   authenticated resume remain unverified.
 
 ## Codex app and instruction import
@@ -129,7 +129,7 @@ or run `session use`; native task identity is required for task-context receipts
 Review/apply context instead binds the machine, user, paths, package, working directory
 and effect-relevant environment. Status receipts describe recorded attempts; `handoff`
 separates package/runtime verification from helper registration, integrity and usability.
-Read-only `try_transaction_lock` in `compose/corpus_transaction.py` permits current
+Read-only `try_transaction_lock` in `compose/instructions_transaction.py` permits current
 checks without waiting for another writer or creating synchronization state. If it
 cannot acquire safe synchronization, handoff reports `verification: "deferred"` and
 unobserved readiness fields as `null`, while status still returns recorded progress.
@@ -141,7 +141,7 @@ skill discovery. The engine does not install or configure the host's file/comman
 
 `app session preview/use/off/status` manages **returned task context**, not a new Codex
 CLI session. This route uses no separate Codex CLI subprocess, no Textual runtime and
-no direct model SDK. Corpus Studio needs a terminal; rich UI remains optional. App use
+no direct model SDK. Instructions Studio needs a terminal; rich UI remains optional. App use
 requires explicit selection, enables no native hooks or agents, and Off cannot retract
 previously returned text. Registration is off by default and owns only its discovery
 link, preserving global instruction files and foreign entries.
@@ -154,17 +154,17 @@ consumption placement and trigger descriptions; it is not a deterministic classi
 Planning/applying requires an installed baseline. Original native files remain intact
 and may still be loaded independently by the host.
 
-## Private corpus assets
+## Private instructions assets
 
-- **Native corpus hooks and agents** require explicit `--corpus-native` and a supported
+- **Native instructions hooks and agents** require explicit `--instructions-native` and a supported
   installed carrier. Claude agents retain their authored frontmatter in per-item
   plugins; names are plugin-qualified. Codex agent-semantic translation remains separate
   work. Neither route registers global hooks by default.
 - **Codex role templates** (`codex/agents/*.toml`) are carried in the immutable private
   release. Private installation does not require copies under the native host home.
 - **Management bootstrap** (`compose/bootstrap/SKILL.md`) and selected requested
-  procedures are private snapshot resources. **No-corpus mode omits the bootstrap and
-  corpus instruction text.** The optional app discovery bridge is a separate entry;
+  procedures are private snapshot resources. **No-instructions mode omits the bootstrap and
+  agent-bios instruction text.** The optional app discovery bridge is a separate entry;
   registration alone does not select task context.
 
 ## Models and optional integrations
@@ -177,7 +177,7 @@ Agent-bios does not install credentials or infer a model account from dependency
   The selected static path needs Python standard libraries for preparation and acceptance;
   rendering additionally needs a job-bound Node executable, Playwright module, `pdf-lib`
   beside that module, and a Chromium-family browser executable. These are not installed
-  by corpus delivery. The 2026-09-09 job verification used Node 24.19.0, Playwright 1.62.1,
+  by instructions delivery. The 2026-09-09 job verification used Node 24.19.0, Playwright 1.62.1,
   pdf-lib 1.17.1 and browser 152.0.7977.83; it is separate from the current host Node report.
 - **Deep review** — uses the configured host CLI rather than another core tool. Codex
   runs its own read-only exec route with a self-contained packet; the frontier model
@@ -190,10 +190,10 @@ Agent-bios does not install credentials or infer a model account from dependency
   binding, reach and fallback are declared in the launch contract. An unavailable or
   unauthenticated opposite-family route is reported, not credited as a completed review.
 - **MCP servers** — user-specific; only a selected capability declaring `mcp-stdio-v1`
-  is registered by the launcher. No shipped review method requires MCP. App corpus
+  is registered by the launcher. No shipped review method requires MCP. App instructions
   context delivery does not add an MCP server.
 - **spreadsheet-processing** — an optional skill referenced by the spreadsheet rule
-  when that corpus is selected. If unavailable, its inline plain-tools/code and real
+  when those instructions are selected. If unavailable, its inline plain-tools/code and real
   spreadsheet-engine validation fallback applies.
 
 Host `config.toml`, `settings.json`, `hooks.json` and credentials are untracked,
@@ -208,7 +208,7 @@ python3 -B - <<'PY'
 import json, os, pathlib, sys
 repo = pathlib.Path.cwd()
 sys.path.insert(0, str(repo / 'compose'))
-from corpus_setup import dependency_inventory
+from instructions_setup import dependency_inventory
 for row in dependency_inventory(repo, {**os.environ, 'PYTHONDONTWRITEBYTECODE': '1'}):
     print(json.dumps({key: row[key] for key in ('id', 'status', 'version', 'path', 'manual_reason')}, ensure_ascii=False))
 PY
@@ -218,7 +218,7 @@ Inspect the installed private state using this checkout's runtime:
 
 ```bash
 bash install.sh verify
-bash install.sh corpus status --json
+bash install.sh instructions status --json
 bash install.sh app status --json
 ```
 
@@ -247,7 +247,7 @@ machine inventory:
 ```bash
 python3 -B - <<'PY'
 import pathlib
-paths = list(pathlib.Path('compose').glob('corpus*.py')) + [pathlib.Path('launch/agent-launch.py')]
+paths = list(pathlib.Path('compose').glob('instructions*.py')) + [pathlib.Path('launch/agent-launch.py')]
 for path in paths:
     compile(path.read_text(), str(path), 'exec')
 PY
@@ -264,8 +264,8 @@ zsh -n launch/agent-launch.zsh
 | `launch/provision-venv.sh` | Textual root pin, `JSONSCHEMA_PIN` and explicit managed package installation |
 | `gates/build-ui-runtime.py` | author-side bundle generation and offline check/self-test |
 | `compose/ui_runtime/manifest.json` | generated exact UI wheel inventory, versions, hashes and licenses |
-| `compose/corpus_ui_runtime.py` | offline verification, process-lifetime extraction and release |
-| `compose/corpus_setup.py` | shared SetupController, local inventory and reviewed dependency recipes |
+| `compose/instructions_ui_runtime.py` | offline verification, process-lifetime extraction and release |
+| `compose/instructions_setup.py` | shared SetupController, local inventory and reviewed dependency recipes |
 | `package.json` and runtime validators | supported platforms and required runtime minimums |
 | guide `Environment Binding` and launch profile | role/model bindings and feature-specific host evidence |
 | guide `Evidence Base` | measured behavior and numeric defaults |

package/INSTALL.md

@@ -74,8 +74,8 @@ resolved paths remain inside the source; do not follow links to outside files:
 
 - `INSTALL.md`
 - `install.sh`
-- `compose/corpus_setup_cli.py`
-- `compose/corpus_setup.py`
+- `compose/instructions_setup_cli.py`
+- `compose/instructions_setup.py`
 - `compose/setup/START.md`
 
 If they are missing, explain that the selected public revision/package does not
@@ -105,8 +105,8 @@ Require a successful JSON response with `kind: "agent-bios-setup-start"`,
 `setup_argv`, keeping the same source, working directory and reviewed execution
 context. Do not fall back to a PATH command if validation fails.
 
-The detailed guide collects corpus, optional dependencies, app connection and
+The detailed guide collects instructions, optional dependencies, app connection and
 instruction-source choices, then prepares the exact review for authorized Apply.
 Use the existing authorization for concrete effects already accepted by the user.
 Preserve global/project `AGENTS.md` and `CLAUDE.md`. Installation and app connection
-do not authorize corpus content in this task; that remains a separate explicit use.
+do not authorize instructions content in this task; that remains a separate explicit use.

package/README.md

@@ -5,21 +5,48 @@
 Build an instruction library you can inspect, edit, and reuse. Choose what each
 CLI session or Codex app task uses, while preserving your existing global instruction files.
 
-[Quick start](#quick-start) · [Corpus Studio](#your-instruction-library) · [How it works](#how-sessions-work) · [Understand!](#understand-the-reasoning) · [Documentation](#documentation) · [한국어](ko/README.md)
+[0.19.2 release notes](docs/releases/0.19.2.md)
 
-![Corpus Studio showing a guide-linked rule and an unapplied on/off choice](docs/assets/corpus-studio.svg)
+## Purpose
 
-*Actual 0.18.0 Studio UI, captured with Textual enabled and the bundled corpus
-in an isolated test environment.*
+<!-- product-purpose:start -->
+agent-bios exists to let workers compose, share, and inherit team work environments
+from Instructions, Domain knowledge, and Decision memory, so they can perform
+their roles within the standards and context of their team, industry, and organization.
+
+A team is the basic unit for selecting, adopting, and sharing a work environment.
+
+Workers should be able to select an environment appropriate to their role and
+team, collaborate from shared standards and decision context, and continue
+the work when a worker, model, session, or device changes. Shared context does
+not require identical outputs or erase personal, team, and organizational boundaries.
+<!-- product-purpose:end -->
+
+The current service provides the Instructions library and host launch/delivery
+integration. Shared environment editions, Domain knowledge, and Decision memory
+are the design direction; this purpose statement does not claim they are shipped.
+
+[Quick start](#quick-start) · [Instructions Studio](#your-instruction-library) · [How it works](#how-sessions-work) · [Understand!](#understand-the-reasoning) · [Documentation](#documentation) · [한국어](ko/README.md)
+
+![Studio showing a guide-linked rule and an unapplied on/off choice](docs/assets/instructions-studio.svg)
+
+*Actual 0.18.0 UI, captured with Textual enabled and the bundled instructions
+in an isolated test environment. This earlier capture retains its Corpus Studio title;
+the current UI is named Instructions Studio.*
 
 ## Make your instructions your own
 
-agent-bios ships a starting library of rules, guides, and procedures, called a
-**corpus**. You decide which parts belong in your working environment.
+agent-bios ships **Instructions**: rules, guides, and procedures for how you work.
+You decide which parts belong in your working environment. The CLI command is
+`instructions`, and the library UI is named **Instructions Studio**.
+
+These names apply to this source revision. If your installed version does not
+recognize `agent-bios instructions`, use `agent-bios corpus`; this revision also
+accepts that older command name. See [compatibility](docs/instructions-compatibility.md).
 
 | What you want to do | What agent-bios provides |
 | --- | --- |
-| See what your instructions say | Browse and search documents in Corpus Studio; follow a rule's links to its guides. |
+| See what your instructions say | Browse and search documents in Instructions Studio; follow a rule's links to its guides. |
 | Adapt them to your work | Edit supplied items, create personal ones, and choose their delivery method. |
 | Choose what a session uses | Switch individual items on or off without deleting their content or edits. |
 | Recover the starting point | Restore supplied content, recover personal items, or preview a full reset. |
@@ -30,7 +57,7 @@ It does not train the model or guarantee that the model follows every instructio
 ## Quick start
 
 Use the terminal installer or set up through a Codex app conversation. Both offer
-language, dependency, corpus and optional app/import choices.
+language, dependency, instructions and optional app/import choices.
 See [setup and prerequisites](docs/setup.md).
 
 ### In a terminal
@@ -39,13 +66,13 @@ You need **macOS or Linux**, **Bash**, **Python 3.11+**, and **Node.js 18+ with
 for package installation. Run:
 
 ```bash
-npm install -g agent-bios@0.19.1
+npm install -g agent-bios@0.19.0
 agent-bios install
 ```
 
 The installer opens a guided terminal UI with English, Korean and Japanese. Its
 verified Textual bundle is included; a separate UI installation is unnecessary.
-Choose only the dependencies and corpus you want. [Full setup options →](docs/setup.md)
+Choose only the dependencies and instructions you want. [Full setup options →](docs/setup.md)
 
 To launch a CLI session, install and authenticate that host CLI, then run this from
 your project:
@@ -60,9 +87,9 @@ Use `codex` instead of `claude` for a Codex CLI session.
 2. Review the model, review setup, and permissions. **Some presets request
    permission bypass**; select settings appropriate for your project.
 3. Start the session. Choose **Software Engineer / Vanilla** to use the host's
-   native setup without an agent-bios corpus snapshot.
+   native setup without an agent-bios instructions snapshot.
 
-Open **Corpus Studio** from the launcher or run `agent-bios corpus` to inspect the
+Open **Instructions Studio** from the launcher or run `agent-bios instructions` to inspect the
 library. `agent-bios status` shows the installed private release and its location.
 
 <details>
@@ -96,18 +123,18 @@ Install https://github.com/kangminlee-maker/agent-bios
 ```
 
 The agent follows [INSTALL.md](INSTALL.md), obtains a fixed source revision, and
-asks for English, 한국어 or 日本語. Choose dependencies, no active corpus or specific
-corpus, and optional app connection or instruction-file capture. Review the effects
+asks for English, 한국어 or 日本語. Choose dependencies, no active instructions or specific
+instructions, and optional app connection or instruction-file capture. Review the effects
 before Apply. You do not need to supply a local path or install Codex CLI.
 
 Once the registered command appears in the app, use `$agent-bios` for setup or management.
-To add corpus to a task, explicitly ask it to use your chosen corpus there.
-Installation and opening Corpus Studio do not activate task context.
-[App use, off, and personal instruction import →](docs/setup.md#use-corpus-in-a-codex-app-task)
+To add instructions to a task, explicitly ask it to use your chosen instructions there.
+Installation and opening Instructions Studio do not activate task context.
+[App use, off, and personal instruction import →](docs/setup.md#use-instructions-in-a-codex-app-task)
 
 ## Your instruction library
 
-Open **Corpus Studio** in the launcher, or run `agent-bios corpus`.
+Open **Instructions Studio** in the launcher, or run `agent-bios instructions`.
 In the app, `$agent-bios` can manage the same library through conversation.
 
 - **Read as you navigate.** Arrow keys move between reading controls and update
@@ -128,7 +155,7 @@ Individual on/off choices take precedence over default domain/core selections.
 Off is not deletion: content and edits remain available, including for learning.
 Updates retain those choices; a full reset returns to installed defaults.
 
-[Corpus controls, keyboard navigation, delivery methods, and included guides →](docs/corpus.md)
+[Instructions controls, keyboard navigation, delivery methods, and included guides →](docs/instructions.md)
 
 ## How sessions work
 
@@ -149,8 +176,8 @@ does not. Project instructions and prior conversation content are separate.
 
 ## Understand the reasoning
 
-Choose **Understand!** in the launcher to explore why the corpus is written the
-way it is. Select a coherent learning bundle rather than memorizing separate files.
+Choose **Understand!** in the launcher to explore why the instructions are written the
+way they are. Select a coherent learning bundle rather than memorizing separate files.
 
 The tutor chooses a small set of core learning points and tracks questions by their
 source bullet. No bullet receives more than ten questions, including follow-ups.
@@ -187,29 +214,29 @@ requires your confirmation.
 | When you need more detail | Read |
 | --- | --- |
 | Install, connect the app, or import existing instructions | [Setup](docs/setup.md) |
-| Author, enable, restore, or inspect corpus items | [Corpus](docs/corpus.md) |
+| Author, enable, restore, or inspect instructions items | [Instructions](docs/instructions.md) |
 | Understand snapshots, storage, and session evidence | [Session model](docs/session-model.md) |
 | Migrate, reset, or resolve installation conflicts | [Recovery](docs/recovery.md) |
 | Configure presets, globals, shell connection, native hooks, or review | [Advanced launch](docs/advanced-launch.md) |
-| Learn the corpus and preserve a discovery | [Understand!](docs/understand.md) |
+| Learn the instructions and preserve a discovery | [Understand!](docs/understand.md) |
 | Check prerequisites and optional tools | [Dependencies](DEPENDENCIES.md) |
 | Develop this repository | [Contributing](CONTRIBUTING.md) — requires a checkout |
 
-Use `agent-bios help` and `agent-bios corpus --help` for command discovery.
+Use `agent-bios help` and `agent-bios instructions --help` for command discovery.
 Source references: [delivery surfaces](SURFACES.md), [network contract](ENDPOINTS.md),
 and [terminology](LEXICON.md).
 
 ## Adopting elsewhere
 
 Review the `(private)` bindings and environment-specific dependencies before
-adopting the defaults. Keep personal adjustments in Corpus Studio, or follow
+adopting the defaults. Keep personal adjustments in Instructions Studio, or follow
 [the source-authoring workflow](CONTRIBUTING.md#adopting-elsewhere) when changing
 what the package ships.
 
 ## Scope
 
 The package contains instruction sources and runtime machinery, not your
-personal corpus state, learning events, session pins, credentials, or native settings.
+personal instructions state, learning events, session pins, credentials, or native settings.
 
 ## License
 

package/claude/CLAUDE.md

@@ -90,7 +90,7 @@
 - For composing a prompt, packet, or tool description aimed at a specific model family — including cross-family review dispatch, porting a prompt written for an older model, or choosing a reasoning-effort level for a model family — read and use `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/guides/gpt-prompting.md` for gpt-family targets and `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/guides/claude-prompting.md` for claude-family targets as scoped extensions of this section.
 - Allocate models by difficulty × blast radius, not phase name; when implementation ran on a cheaper tier, compensate by raising reviewer effort or adding a reviewer kind — never economize on implementation and verification at once.
 - Judge a review by how much independence it actually bought, per reviewer and in this order: different provider, then different model, then strictly higher effort, then the two-perspective floor. A lower effort earns nothing — cheaper is not another perspective. Isolation is a gate rather than a rung: a reviewer you cannot show ran in a fresh context is not a weak review but no review, so exclude it instead of grading it low. Several ready methods are coverage, not proof the perspectives differed; and a clean verdict is PROPOSED until a receipt evidences a fresh dispatch of the declared packet on the exact seat, since a model echo is not evidence.
-- When the user asks for design AND two or more providers are reachable at frontier tier, run dual-provider frontier design drafts: two independent drafts from the same blind packet, one per provider, compared and synthesized into the working draft. The consent gate is about metered spend, not the fan-out: a provider reached via an OAuth session (subscription-covered, no marginal cost) proceeds WITHOUT asking — if a non-main-context OAuth frontier provider exists, just run the dual-provider design; do not ask. Explicit per-request approval (never standing) is required ONLY before dispatching to a provider reachable solely via a metered API key, and it approves that spend. If withholding un-approved API spend leaves fewer than two providers, run single-provider rather than blocking the design on approval. Inject the corpus design principles (concept economy, LLM/capability boundary, staged workflow) into every dispatched design packet — an external model does not load this corpus.
+- When the user asks for design AND two or more providers are reachable at frontier tier, run dual-provider frontier design drafts: two independent drafts from the same blind packet, one per provider, compared and synthesized into the working draft. The consent gate is about metered spend, not the fan-out: a provider reached via an OAuth session (subscription-covered, no marginal cost) proceeds WITHOUT asking — if a non-main-context OAuth frontier provider exists, just run the dual-provider design; do not ask. Explicit per-request approval (never standing) is required ONLY before dispatching to a provider reachable solely via a metered API key, and it approves that spend. If withholding un-approved API spend leaves fewer than two providers, run single-provider rather than blocking the design on approval. Inject the instructions design principles (concept economy, LLM/capability boundary, staged workflow) into every dispatched design packet — an external model does not load these instructions.
 - Never retry-storm a live rate limit: give unattended batches you author a code-level circuit breaker with per-item completion tracking (thresholds, backoff, and dead-letter rules in the guide); for third-party dispatchers, confirm equivalent protection exists or attend the run.
 - On any resumed, cleared, or relocated session, re-verify where you are (pwd; in a repo, branch and HEAD) before acting on prior-session assumptions — against the pinned handoff state when one exists.
 

package/claude/guides/claude-prompting.md

@@ -49,7 +49,7 @@ Claude.
 
 Use the shared recipe and checklist together with the section for the model being
 prompted, even when a subagent uses a different model from the main. Model-specific
-tuning preserves the corpus's permission boundaries and required verification.
+tuning preserves the instructions' permission boundaries and required verification.
 
 | Target | Apply |
 | --- | --- |

package/claude/guides/cli-multi-model-workflow.md

@@ -35,7 +35,7 @@ Scoped extension of the global Multi-Model Workflow rules. Rules use portable ro
 
 Main-context pollution is usually costlier than spawn overhead. Apply these gates in order; the first that fires decides:
 
-1. **Independence:** verification and review go outside your own reasoning, not merely outside your conversation. A child carries the standing corpus on both hosts, except Claude's built-in `Explore` and `Plan`, which omit the CLAUDE.md hierarchy. Otherwise a Claude child starts fresh, while Codex `spawn_agent` forks by default — `fork_turns` defaults to `all`, so the child also holds the parent's turn input unless the call passes `none` or a turn count. What a spawn buys is graded by the seat — see Review Independence — never by the fact that it happened.
+1. **Independence:** verification and review go outside your own reasoning, not merely outside your conversation. A child carries the standing instructions on both hosts, except Claude's built-in `Explore` and `Plan`, which omit the CLAUDE.md hierarchy. Otherwise a Claude child starts fresh, while Codex `spawn_agent` forks by default — `fork_turns` defaults to `all`, so the child also holds the parent's turn input unless the call passes `none` or a turn count. What a spawn buys is graded by the seat — see Review Independence — never by the fact that it happened.
    Verify a spawn from the artifact: Claude writes the child to its own `agent-<id>.jsonl` beside the session transcript; Codex writes a rollout whose header carries `parent_thread_id`, `agent_nickname`, `agent_path`, `agent_role`. Codex's `--json` stream cannot see a spawn at all — its `collab_tool_call` object is identical whether or not one occurred.
 2. **Parallelism:** independent items spawn in parallel with per-item tracking.
 3. **Residual context:** spawn work whose working log is much larger than the conclusion the main needs, such as broad reads, searches, tests, or implementation bursts.
@@ -70,7 +70,7 @@ Delegate execution, not decisions. A unit is delegable only when it is decision-
 - Idle/progress notifications are hypotheses; verify repo artifacts before re-dispatch. An idle signal is liveness decoupled from the report: a subagent can go idle without ever delivering its result, so idle-without-report is not done — request the report explicitly rather than waiting. Cross-reset state belongs in files, not task boards or transcripts. When polling concurrent async jobs, pin the exact id/handle received at dispatch — a "latest" convenience selector can silently point at a sibling job and return plausible-but-wrong results.
 - Give reviewers/subagents a read-only diff, snapshot, or isolated worktree — not the live tree the main is editing — and forbid destructive git ops (checkout --, reset --hard, stash, clean) on any tree with uncommitted work; re-verify tree integrity before trusting results produced mid-edit.
 - Codex `spawn_agent` decides how much of the parent crosses: `fork_turns` defaults to `all`, and takes `none` or a turn count. A `SubagentStart` hook there receives `agent_type` and may return `continue: false`, so a tier rule can be enforced rather than stated.
-- No per-spawn corpus suppression exists on either host: the subagent definition carries model and effort, not scope. Excluding the standing instructions is a process-level act — `claude --setting-sources ''`, or `CODEX_HOME` pointed at a directory holding only `auth.json` — and it removes the tier definitions with them, so a corpus-free reader and a pinned tier cannot come from one process. An emptied `CODEX_HOME` without `auth.json` fails 401; skills still load.
+- No per-spawn instructions suppression exists on either host: the subagent definition carries model and effort, not scope. Excluding the standing instructions is a process-level act — `claude --setting-sources ''`, or `CODEX_HOME` pointed at a directory holding only `auth.json` — and it removes the tier definitions with them, so a reader without those instructions and a pinned tier cannot come from one process. An emptied `CODEX_HOME` without `auth.json` fails 401; skills still load.
 - Review cost scales with the diff, so layered review preserves delegation savings. Lower reviewer tier before dropping a review kind.
 
 ## Driving Codex CLI Directly
@@ -143,7 +143,7 @@ How much independence a review actually bought, as an ordinal grade per reviewer
 
 - Trigger: the task is design — high-level shape and implementation process, before any code — AND two or more providers are reachable at frontier tier. Reachability via an OAuth session is subscription-covered — no marginal spend, so no approval and no question: if a non-main-context OAuth frontier provider exists, proceed with the dual-provider design directly. The consent gate applies ONLY to a provider reachable solely via a metered API key: dispatching to it needs the user's explicit per-request approval of that spend (per-request, not standing — an old approval does not carry to the next design). If the only way to reach a second provider is un-approved metered API spend, stay single-provider rather than blocking the design.
 - Mechanics: compose ONE blind packet (evidence, constraints, rubric, neutral alternatives — the escalation-gate packet shape) and dispatch it unchanged to one frontier-tier model per provider; drafts stay independent — neither sees the other's output. Then adjudicate: compare the two dual-provider frontier design drafts against the rubric, take the winner as the skeleton, graft the loser's superior parts, and record what differed and why the synthesis chose as it did (FRONTIER disposition line).
-- Packet injection: a dispatched designer is hermetic — it reads only its packet and never loads this corpus. Inject the design principles the corpus would have supplied: concept economy (reuse/extend/rename/split, compact concept graph), the LLM/tools-code capability boundary, the staged design rules (smallest viable path, falsifiable done-when), and any domain-specific principles the design touches. A draft produced without the principles is not comparable to one produced with them.
+- Packet injection: a dispatched designer is hermetic — it reads only its packet and never loads these instructions. Inject the design principles the instructions would have supplied: concept economy (reuse/extend/rename/split, compact concept graph), the LLM/tools-code capability boundary, the staged design rules (smallest viable path, falsifiable done-when), and any domain-specific principles the design touches. A draft produced without the principles is not comparable to one produced with them.
 
 ## Unattended Batch Safety
 

package/claude/guides/documentation-hygiene.md

@@ -17,6 +17,9 @@ core_rules:
 
 # Documentation Hygiene
 
+Before writing, revising, or translating Korean prose, read and apply
+`${CLAUDE_CONFIG_DIR:-$HOME/.claude}/guides/korean-writing.md` in full.
+
 A scoped extension of the global Documentation Hygiene section. The subject is placement: **prose
 about the past and prose about the present need different addresses.**
 

package/claude/guides/gpt-prompting.md

@@ -225,7 +225,7 @@ that sample, not Astra measurements or promised gains on another workload.
 
 The GPT-5.6 section is derived from `prompt-guidance-gpt-5p6`; the GPT-6 Astra
 section from `model-guidance-gpt-6-astra`. The shared recipe retains task, evidence,
-tool, and validation practices from the GPT-5.6 guidance and the corpus; model
+tool, and validation practices from the GPT-5.6 guidance and the instructions; model
 behavior claims belong only to their matching section. `source_pins` records the
 exact bytes used for this derivation so later vendor edits can be detected.
 

package/claude/guides/korean-writing.md

@@ -0,0 +1,153 @@
+---
+guide_id: korean-writing
+language: en
+status: active
+description: Before writing, revising, or translating Korean prose, you must read and apply this entire guide, including for responses, documents, slide wording, and UI copy.
+use_when:
+  - writing, revising, or translating Korean responses or documents
+  - composing Korean slide text, headlines, buttons, or status labels
+core_rules:
+  - Consult the full guide before Korean writing and compare the result with the source and actual state.
+  - Connect the central judgment to evidence while preserving distinct concepts, conditions, and uncertainty.
+  - Distinguish proposals, available actions, and completed states; match action copy to actual behavior.
+---
+
+# Writing in Korean
+
+Before writing, revising, or translating Korean prose, read and apply this entire guide.
+If the same complete text is already in the current task context, no duplicate file read is needed.
+Apply it to responses, reports, notices, slide wording, and UI copy while respecting the requested
+length, format, and register. Do not force a headline or lengthy evidence onto a short response.
+Preserve quotations and identifiers that must remain exact.
+
+First decide what the reader needs to understand or judge. Connect the supporting evidence and
+conditions, and preserve conceptual distinctions and factual scope when shortening the text.
+The Korean golden sentences below are hypothetical teaching examples, not real facts or fixed
+templates. Apply their preservation of meaning, rather than copying sentence counts, headings,
+or endings.
+
+## 1. Define the question and central judgment
+
+Make each fact, comparison, and explanation's role in the central judgment clear. Split independent
+questions, or explain why they belong together.
+
+- Avoid: “문의가 늘었다. 담당자는 세 명이다. 안내 문서를 개편했다.”
+- Golden: “반복 문의를 줄이기 위해 안내 문서를 개편했다. 담당자 세 명이 자주 받는 질문을 모아 답변을 보강했다.”
+
+Use this connection only when the purpose and work described in the golden are supported.
+Do not invent purpose or activities from a list of facts alone.
+
+## 2. Make the subject and central judgment visible in the headline
+
+Avoid references that require earlier text or headlines that only preview a count. The argument
+should connect when headlines are read alone. Do not force a conclusion onto an overview,
+definition, or transition.
+
+- Avoid: “세 가지 개선 사항”
+- Golden: “신청 절차를 줄여 사용자의 입력 부담을 낮춘다”
+
+For a definition, a role-revealing title such as “신청 자격의 정의” is also appropriate.
+
+## 3. Keep claims within the evidence's scope and certainty
+
+Distinguish hypotheses from confirmed facts, examples from actual selections, and temporal order
+from causality. Retain uncertainty where the source has not established a relationship.
+
+- Avoid: “안내 문서 개편으로 문의가 감소했다.”
+- Golden: “안내 문서 개편 후 문의가 감소했다. 다만 같은 기간 이용자 수도 줄어, 개편의 효과인지는 확인되지 않았다.”
+
+Mention the decline in users only when supported too. Do not invent another fact to explain an
+unconfirmed cause.
+
+## 4. Use the same name for the same concept and distinguish different concepts
+
+Do not alternate synonyms merely for stylistic variety. Even when shortening an explanation,
+retain each independent concept's name, definition, and difference from others.
+
+- Avoid: “활성 사용자는 주간 이용자를 뜻한다. 참여 고객은 이번 주 120명이다.”
+- Golden: “활성 사용자는 일주일 동안 한 번 이상 서비스를 이용한 사용자다. 이번 주 활성 사용자는 120명이다.”
+
+Use the source or agreed definition. Ambiguous terminology does not authorize a new threshold.
+
+## 5. Preserve the subject and action even in short wording
+
+Qualify ambiguous words such as scope, criteria, or completion with the object the reader needs.
+Do not fill gaps in compressed wording with meaning absent from the source.
+
+- Avoid: “통과 범위와 보완 항목을 함께 남깁니다.”
+- Golden: “검토를 통과한 범위와 보완할 항목을 함께 기록합니다.”
+
+Name each state the reader must distinguish directly.
+
+- Avoid: “0처럼 보이는 누락을 구분합니다.”
+- Golden: “값이 누락된 경우와 실제 금액이 0인 경우를 구분합니다.”
+
+## 6. State relationships between concepts explicitly
+
+Make clear what causes, conditions, or forms part of what, and what is compared with what.
+Do not add unsupported causality, sequence, or superiority to create a connection.
+
+- Avoid: “교육 참여와 배포 권한은 연결됩니다.”
+- Golden: “교육 이수는 배포 권한을 신청하기 위한 조건입니다. 교육을 이수해도 권한이 자동으로 부여되지는 않습니다.”
+
+## 7. Move from judgment to evidence
+
+Present the central judgment and necessary premises, then the supporting explanation. Distinguish
+new implications derived from the explanation and avoid repeating the same content in several places.
+
+- Avoid: “연동 시험 두 건이 남았다. 금요일에 시험 환경을 사용할 수 있다. 출시 일정 조정이 필요하다.”
+- Golden: “출시를 다음 주로 미뤄야 한다. 필수 연동 시험 두 건이 남아 있으며, 시험 환경은 이번 주 금요일부터 사용할 수 있다.”
+
+This example assumes the release timing and mandatory tests are established. Do not settle a
+schedule or condition absent from the source.
+
+## 8. Keep conditions, exceptions, and scope close to the claim
+
+Do not relegate interpretation-changing conditions to incidental information. Align units, periods,
+subjects, and denominators when comparing numbers; disclose differences in the comparison bases.
+
+- Avoid: “모든 사용자는 신청을 취소할 수 있다.”
+- Golden: “사용자는 승인 전까지 신청을 취소할 수 있다. 승인 후에는 담당자에게 취소를 요청해야 한다.”
+
+## 9. Distinguish proposals, available actions, and completed states
+
+Do not describe a proposed procedure as an implemented feature. Name what has completed and
+keep review, approval, finalization, and transmission as distinct states.
+
+- Avoid, on a proposal screen before implementation: “원천 자료부터 회계 시스템 입력용 집계까지 검토합니다.”
+- Golden: “원천 자료부터 회계 시스템 입력용 집계까지, 검토 절차를 제안합니다.”
+
+- Avoid: “검토가 완료되어 회계 처리가 끝났습니다.”
+- Golden: “검토를 완료했습니다. 회계 승인과 결산 확정 여부는 별도로 확인해야 합니다.”
+
+## 10. Match action copy to actual behavior
+
+Buttons and links should say what the user will do or see. Distinguish viewing, selecting, saving,
+and submitting. Do not promise a result that the click alone does not achieve.
+
+- Avoid, on a button opening a scope explanation: “검토 시작”
+- Golden: “검토 범위 안내 보기”
+
+If the destination actually allows selection, use “검토 기간·상품 선택”.
+
+## 11. Remove repetition while retaining necessary explanation
+
+Do not delete essential evidence, definitions, or conditions for brevity. Do not add claims or
+repeat statements to fill space. Separate sentences with different roles, such as definition
+and interpretation.
+
+- Avoid: “처리 시간을 단축하고 더 빠르게 처리하기 위해 중복 확인 절차를 없애 처리 속도를 개선한다.”
+- Golden: “처리 시간을 줄이기 위해 같은 정보를 두 번 확인하는 절차를 한 번으로 합친다.”
+
+## 12. Compare the finished text with the source and actual state
+
+Check that key concepts, figures, conditions, subjects, and relationships survive. For features
+and procedures, also verify available behavior and current state. The headlines and body should
+communicate the argument without the author's additional explanation.
+
+- Source: “시범 운영에 참여한 20개 팀 중 12개 팀이 다음 분기에도 사용할 의향이 있다고 답했다.”
+- Avoid: “고객의 60%가 재계약을 확정했다.”
+- Golden: “시범 운영에 참여한 20개 팀 중 12개 팀(60%)이 다음 분기에도 사용할 의향을 밝혔다.”
+
+Preserve the subject, denominator, and response meaning when summarizing. Do not turn intent
+to use into a confirmed renewal.