cc-suite Domain Vocabulary
The canonical noun-and-verb set for cc-suite. Every artifact name, prose description, and rule wording should draw from this registry. Drift between canonical terms and declared deprecated synonyms is flagged by /nlpm:check and penalized by /nlpm:score when R51 is enabled.
Status: seeded by /nlpm:vocab-init on 2026-05-26 and pruned during the initial migration pass. Only deprecation pairs that can be cleanly enforced (no false positives in the current corpus) are in registry.yaml. Other observed drift is documented below as convention-only with the rationale for non-enforcement.
Scopes
cc-suite has a single scope. Unlike NLPM (internal + auditor), cc-suite's artifacts all describe one system — the bridge between Claude Code, Codex CLI, and Antigravity CLI (agy).
| Scope |
Paths |
Description |
internal |
commands/, skills/cc-suite/, templates/agents/, AGENTS.md |
The cc-suite bridge subsystem itself. |
Enforced deprecation pairs (R51 will flag these)
These are clean drifts: the canonical term has fully replaced the deprecated one in the corpus, and the deprecated term has no remaining legitimate uses.
| Canonical |
Deprecated synonym |
Status |
dimension |
pillar |
Fully migrated (Mar 2026). All 5 audit-family commands now use Dimension N: headings and (N dimensions) phrasing. |
subagent |
sub-agent |
Fully migrated. The hyphenated form was a typo accident in agent-design SKILL.md and audit-agent.md. |
refresh |
freshen |
Fully migrated. freshen-aware / freshen semantics in AGENTS.md rewritten to refresh-aware / refresh semantics. |
Canonical-only verbs (no deprecation; just the canonical form)
Used to establish the cc-suite verb vocabulary so new artifacts pick from this set rather than coining synonyms. R51 doesn't penalize anything here because no observed drift exists.
| Canonical |
Definition |
audit |
Structured multi-dimension code/artifact scan with severity table (Codex-delegated). |
bridge |
Umbrella verb for making one tool's config visible to another. |
update |
User-side coupled re-render after claude plugin update cc-suite (slash command). |
init |
First-time project setup of all cc-suite bridge artifacts. |
check |
Lightweight prerequisite / connectivity probe. |
consult |
Invoke a cc-suite advisor and receive its judgment. |
delegate |
Forward a task to Claude Code via mcp__claude-code__claude_code. |
fix |
Code-level remediation of a specific reported defect (distinct from repair). |
repair |
Non-interactive re-run of all bridge / registration scripts (distinct from fix). |
verify |
Confirm a prior code-fix outcome via Claude MCP. |
register |
Persist an MCP server entry into .mcp.json or .codex/config.toml. |
expose |
Symlink-based sub-operation of bridge for cc-suite plugin skills. |
mirror |
One-directional copy sub-operation of bridge for hooks and MCP. |
setup |
Higher-level user activity composed of init + configure + verify. |
review |
Send a plan or PR to Codex for architectural review (distinct from consult). |
cancel continue implement plan analyze result status add remove list preflight unbridge |
Single-command verbs; one canonical, no competing synonyms observed. |
Canonical-only nouns
| Canonical |
Definition |
advisor |
A project-scoped value-over-rules persona declared in .cc-suite/agents/, backed by claude-octopus as a separately-configured MCP server. |
bridge |
The cc-suite-managed subsystem that wires Claude Code, Codex, and Antigravity (agy) together. |
finding |
A single defect surfaced by an audit/review — file:line, severity, recommendation. Use in structured audit output (column headers, "Top Findings" sections, per-finding iteration in audit-fix/verify). |
sentinel block |
The cc-suite-owned section in .codex/config.toml or .gitignore, delimited by sentinel comments. |
thread |
The Codex execution-continuation handle (the threadId MCP parameter). |
registration |
The persisted MCP server entry produced by bridge. |
preset |
A starter advisor agent file shipped under templates/agents/. |
pin |
The version string for claude-octopus in scripts/lib/claude-octopus-pin.txt. |
timeline |
The per-advisor persistent consultation history at .cc-suite/agents/<name>/timeline/. |
artifact |
A file cc-suite owns — command, skill, agent, hook, manifest, config. |
script |
An executable under scripts/ — bash, python, or mjs. |
Role-noun suffixes for advisor preset names (intentional sub-variants)
These are not drift — each suffix encodes the persona's stance.
| Suffix |
Stance |
Example preset |
_advisor |
General-purpose value advisor; broad-scope judgment. |
north_star_advisor |
_reviewer |
Reviews finished work against a single quality dimension. |
clarity_reviewer |
_critic |
Judges the output of an upstream process (typically docs). |
documentation_critic |
_advocate |
Argues for one specific action over alternatives. |
deletion_advocate, simplicity_advocate |
_skeptic |
Adversarial reviewer; assumes hostile inputs / worst case. |
security_skeptic |
When introducing a new preset, pick the suffix that best matches its stance. Default to _advisor when none fit.
Why these pairs are convention-only (not enforced by R51)
The /nlpm:vocab-drift scan surfaced the drift candidates listed below. Each looks like a clean canonical/deprecated pair but turns out to be polysemous in cc-suite. R51 is mechanical — it flags every occurrence of a deprecated term regardless of context — so declaring these would generate false-positive penalties on legitimate uses. They are conventions, not rules:
| Concept pair |
Why we don't enforce |
finding ← issue |
finding is canonical for audit-output rows (column headers, Top Findings sections, per-finding iteration in audit-fix.md / verify.md). But issue legitimately means a different thing elsewhere: infrastructure problem in diagnose.md ("Found N issues. Fix them?"), implementation hiccup in implement.md ("Issues encountered"), code-quality category in audit prose ("minor clarity issues"). A blanket deprecation would mis-rename all three contexts. Convention: structured rows say Finding; everything else stays issue. |
advisor ← agent |
advisor is canonical for cc-suite personas in prose. But agent is unavoidable in file paths (.cc-suite/agents/, templates/agents/), command names (add-agent, remove-agent, list-agents) — chosen to match Claude Code's .claude/agents/ convention — and refers to Claude Code's native subagent concept in design discussions. Convention: speak about "advisors" in prose; keep the file/dir/command layout using agent. |
thread ← session |
thread is canonical for the Codex execution-continuation handle. session appears in continue.md's description as user-facing language ("Continue a previous Codex session"). Convention: prefer thread in technical contexts; tolerate session in user-facing descriptions. |
delegate ← ask / send |
delegate is canonical in skill bodies. ask and send appear in description: frontmatter openings of the claude-* skills because they're more natural English for a one-line summary. Convention: skill body uses delegate; frontmatter description allows either. |
preset ← template |
preset is the user-facing concept. template is the directory name (templates/agents/) and appears in add-agent.md frontmatter where it accurately describes what gets copied. Convention: speak about "presets" in prose; the on-disk word is template. |
verify ← check |
verify is canonical for code-fix-outcome confirmation. check covers infrastructure probes (Step 2: Run additional deep checks in diagnose.md). Convention: don't conflate. |
How to extend
Re-run extraction:
python3 ${CLAUDE_PLUGIN_ROOT:-~/.claude/plugins/cache/xiaolai/nlpm/1.0.0}/analysis/scripts/extract-vocabulary.py \
--root . \
--scopes analysis/vocab-init-scopes.json \
--out analysis/vocabulary-extract/
New terms appear in analysis/vocabulary-extract/summary.md.
Add a row to the matching table above (Verbs or Nouns, in the correct scope). Cite at least one file as evidence.
To deprecate a synonym, add it to the canonical term's deprecated: list in registry.yaml AND update the "Enforced deprecation pairs" table above. Before doing this, run grep -r "<deprecated>" and confirm the term has no legitimate alternate meanings — if it does, document the pair in "Why these pairs are convention-only" instead.
Adopting R51
To turn on vocabulary drift detection on this project, add to .claude/nlpm.local.md:
rule_overrides:
R51:
enabled: true
vocabulary_skill: skills/cc-suite/vocabulary/
The pruned registry should produce zero R51 findings on the current corpus.
See also
- The corpus extractor:
${NLPM_ROOT}/analysis/scripts/extract-vocabulary.py
- The six design principles:
${NLPM_ROOT}/analysis/vocabulary-design-principles.md
- Run
/nlpm:vocab-drift periodically to surface new candidate pairs as the corpus grows.
Example Invocations
1---2name: vocabulary-43description: Use when writing, reviewing, or naming any cc-suite artifact — pick the canonical noun or verb from this registry rather than coining a synonym. Loaded by NLPM's scorer and checker when R51 is enabled in .claude/nlpm.local.md.4---56# cc-suite Domain Vocabulary78> The canonical noun-and-verb set for cc-suite. Every artifact name, prose description, and rule wording should draw from this registry. Drift between canonical terms and declared deprecated synonyms is flagged by `/nlpm:check` and penalized by `/nlpm:score` when R51 is enabled.9>10> **Status:** seeded by `/nlpm:vocab-init` on 2026-05-26 and pruned during the initial migration pass. Only deprecation pairs that can be cleanly enforced (no false positives in the current corpus) are in `registry.yaml`. Other observed drift is documented below as **convention-only** with the rationale for non-enforcement.1112---1314## Scopes1516cc-suite has a single scope. Unlike NLPM (internal + auditor), cc-suite's artifacts all describe one system — the bridge between Claude Code, Codex CLI, and Antigravity CLI (`agy`).1718| Scope | Paths | Description |19|-------|-------|-------------|20| `internal` | `commands/`, `skills/cc-suite/`, `templates/agents/`, `AGENTS.md` | The cc-suite bridge subsystem itself. |2122## Enforced deprecation pairs (R51 will flag these)2324These are clean drifts: the canonical term has fully replaced the deprecated one in the corpus, and the deprecated term has no remaining legitimate uses.2526| Canonical | Deprecated synonym | Status |27|-----------|--------------------|--------|28| `dimension` | `pillar` | Fully migrated (Mar 2026). All 5 audit-family commands now use `Dimension N:` headings and `(N dimensions)` phrasing. |29| `subagent` | `sub-agent` | Fully migrated. The hyphenated form was a typo accident in agent-design SKILL.md and audit-agent.md. |30| `refresh` | `freshen` | Fully migrated. `freshen-aware` / `freshen semantics` in AGENTS.md rewritten to `refresh-aware` / `refresh semantics`. |3132## Canonical-only verbs (no deprecation; just the canonical form)3334Used to establish the cc-suite verb vocabulary so new artifacts pick from this set rather than coining synonyms. R51 doesn't penalize anything here because no observed drift exists.3536| Canonical | Definition |37|-----------|------------|38| `audit` | Structured multi-dimension code/artifact scan with severity table (Codex-delegated). |39| `bridge` | Umbrella verb for making one tool's config visible to another. |40| `update` | User-side coupled re-render after `claude plugin update cc-suite` (slash command). |41| `init` | First-time project setup of all cc-suite bridge artifacts. |42| `check` | Lightweight prerequisite / connectivity probe. |43| `consult` | Invoke a cc-suite advisor and receive its judgment. |44| `delegate` | Forward a task to Claude Code via `mcp__claude-code__claude_code`. |45| `fix` | Code-level remediation of a specific reported defect (distinct from `repair`). |46| `repair` | Non-interactive re-run of all bridge / registration scripts (distinct from `fix`). |47| `verify` | Confirm a prior code-fix outcome via Claude MCP. |48| `register` | Persist an MCP server entry into `.mcp.json` or `.codex/config.toml`. |49| `expose` | Symlink-based sub-operation of `bridge` for cc-suite plugin skills. |50| `mirror` | One-directional copy sub-operation of `bridge` for hooks and MCP. |51| `setup` | Higher-level user activity composed of init + configure + verify. |52| `review` | Send a plan or PR to Codex for architectural review (distinct from `consult`). |53| `cancel` `continue` `implement` `plan` `analyze` `result` `status` `add` `remove` `list` `preflight` `unbridge` | Single-command verbs; one canonical, no competing synonyms observed. |5455## Canonical-only nouns5657| Canonical | Definition |58|-----------|------------|59| `advisor` | A project-scoped value-over-rules persona declared in `.cc-suite/agents/`, backed by `claude-octopus` as a separately-configured MCP server. |60| `bridge` | The cc-suite-managed subsystem that wires Claude Code, Codex, and Antigravity (`agy`) together. |61| `finding` | A single defect surfaced by an audit/review — file:line, severity, recommendation. Use in structured audit output (column headers, "Top Findings" sections, per-finding iteration in audit-fix/verify). |62| `sentinel block` | The cc-suite-owned section in `.codex/config.toml` or `.gitignore`, delimited by sentinel comments. |63| `thread` | The Codex execution-continuation handle (the `threadId` MCP parameter). |64| `registration` | The persisted MCP server entry produced by `bridge`. |65| `preset` | A starter advisor agent file shipped under `templates/agents/`. |66| `pin` | The version string for `claude-octopus` in `scripts/lib/claude-octopus-pin.txt`. |67| `timeline` | The per-advisor persistent consultation history at `.cc-suite/agents/<name>/timeline/`. |68| `artifact` | A file cc-suite owns — command, skill, agent, hook, manifest, config. |69| `script` | An executable under `scripts/` — bash, python, or mjs. |7071### Role-noun suffixes for advisor preset names (intentional sub-variants)7273These are **not drift** — each suffix encodes the persona's stance.7475| Suffix | Stance | Example preset |76|--------|--------|----------------|77| `_advisor` | General-purpose value advisor; broad-scope judgment. | `north_star_advisor` |78| `_reviewer` | Reviews finished work against a single quality dimension. | `clarity_reviewer` |79| `_critic` | Judges the output of an upstream process (typically docs). | `documentation_critic` |80| `_advocate` | Argues for one specific action over alternatives. | `deletion_advocate`, `simplicity_advocate` |81| `_skeptic` | Adversarial reviewer; assumes hostile inputs / worst case. | `security_skeptic` |8283When introducing a new preset, pick the suffix that best matches its stance. Default to `_advisor` when none fit.8485## Why these pairs are convention-only (not enforced by R51)8687The `/nlpm:vocab-drift` scan surfaced the drift candidates listed below. Each looks like a clean canonical/deprecated pair but turns out to be **polysemous** in cc-suite. R51 is mechanical — it flags every occurrence of a deprecated term regardless of context — so declaring these would generate false-positive penalties on legitimate uses. They are conventions, not rules:8889| Concept pair | Why we don't enforce |90|--------------|----------------------|91| `finding` ← `issue` | `finding` is canonical for audit-output rows (column headers, `Top Findings` sections, per-finding iteration in `audit-fix.md` / `verify.md`). But `issue` legitimately means a different thing elsewhere: infrastructure problem in `diagnose.md` ("Found N issues. Fix them?"), implementation hiccup in `implement.md` ("Issues encountered"), code-quality category in audit prose ("minor clarity issues"). A blanket deprecation would mis-rename all three contexts. **Convention**: structured rows say `Finding`; everything else stays `issue`. |92| `advisor` ← `agent` | `advisor` is canonical for cc-suite personas in prose. But `agent` is unavoidable in file paths (`.cc-suite/agents/`, `templates/agents/`), command names (`add-agent`, `remove-agent`, `list-agents`) — chosen to match Claude Code's `.claude/agents/` convention — and refers to Claude Code's native subagent concept in design discussions. **Convention**: speak about "advisors" in prose; keep the file/dir/command layout using `agent`. |93| `thread` ← `session` | `thread` is canonical for the Codex execution-continuation handle. `session` appears in `continue.md`'s description as user-facing language ("Continue a previous Codex session"). **Convention**: prefer `thread` in technical contexts; tolerate `session` in user-facing descriptions. |94| `delegate` ← `ask` / `send` | `delegate` is canonical in skill bodies. `ask` and `send` appear in `description:` frontmatter openings of the claude-* skills because they're more natural English for a one-line summary. **Convention**: skill body uses `delegate`; frontmatter description allows either. |95| `preset` ← `template` | `preset` is the user-facing concept. `template` is the directory name (`templates/agents/`) and appears in `add-agent.md` frontmatter where it accurately describes what gets copied. **Convention**: speak about "presets" in prose; the on-disk word is `template`. |96| `verify` ← `check` | `verify` is canonical for code-fix-outcome confirmation. `check` covers infrastructure probes (`Step 2: Run additional deep checks` in `diagnose.md`). **Convention**: don't conflate. |9798---99100## How to extend1011021. Re-run extraction:103104 ```bash105 python3 ${CLAUDE_PLUGIN_ROOT:-~/.claude/plugins/cache/xiaolai/nlpm/1.0.0}/analysis/scripts/extract-vocabulary.py \106 --root . \107 --scopes analysis/vocab-init-scopes.json \108 --out analysis/vocabulary-extract/109 ```1101112. New terms appear in `analysis/vocabulary-extract/summary.md`.1123. Add a row to the matching table above (Verbs or Nouns, in the correct scope). Cite at least one file as evidence.1134. To deprecate a synonym, add it to the canonical term's `deprecated:` list in `registry.yaml` AND update the "Enforced deprecation pairs" table above. Before doing this, run `grep -r "<deprecated>"` and confirm the term has no legitimate alternate meanings — if it does, document the pair in "Why these pairs are convention-only" instead.114115## Adopting R51116117To turn on vocabulary drift detection on this project, add to `.claude/nlpm.local.md`:118119```yaml120rule_overrides:121 R51:122 enabled: true123 vocabulary_skill: skills/cc-suite/vocabulary/124```125126The pruned registry should produce zero R51 findings on the current corpus.127128## See also129130- The corpus extractor: `${NLPM_ROOT}/analysis/scripts/extract-vocabulary.py`131- The six design principles: `${NLPM_ROOT}/analysis/vocabulary-design-principles.md`132- Run `/nlpm:vocab-drift` periodically to surface new candidate pairs as the corpus grows.133134## Example Invocations135136<example>137Context: An author is naming a new action in a command file and wants the approved verb.138user: "My new command looks for outdated config entries — what should I call that action?"139assistant: "I'll check the vocabulary registry before naming it, so this lands on the canonical verb instead of coining a synonym that R51 will flag later."140</example>141142<example>143Context: The scorer flagged a deprecated term and the author needs the canonical replacement.144user: "R51 flagged a deprecated synonym in this file — what am I supposed to write instead?"145assistant: "I'll look the flagged word up in the enforced deprecation pairs table below and use the canonical column's value as the replacement."146</example>
xiaolai