docs/adapters/terminology-and-structure-gaps/binary-renames
Binary Renames reference
Private (non-publishable) §3.2 workspaces keep their dev-only bins (kip, kip-mcp,
Continue reading
Nearby pages in the same section.
Binary Renames
**Superseded by spec 15** (
docs/specs/platform-gaps/15-private-isolation-rename.md§3"Single-bin policy" and the §3.1 "Bin(s)" column), executed by WP-RN-06
(
docs/specs/platform-gaps/phase1/rn-06-bins.md). The original plan below aligned thepublic
@a5c-ai/*train on anadapters-{feature}pattern with one-major deprecatedaliases; the private
@fabricstack/*train ships neutral per-component bin names and**drops every legacy alias instead of aliasing it** (D10: no compatibility shims; D17: the
public repo keeps the old bins for old users). This table is the tool input of
scripts/check-binary-renames.cjs(npm run test:binary-renames).
Private-train bins (spec 15 §3.1, shipped)
| Bin | Package | Entry (file names keep their RN-1 spelling; RN-4 renames identifiers) | Replaces (public train, dropped) |
|---|---|---|---|
orchestrator | @fabricstack/orchestrator | bin/babysitter.js | babysitter |
orchestrator-sdk | @fabricstack/orchestrator-sdk | dist/cli/main.js | babysitter-sdk, babysitter (duplicate) |
orchestrator-mcp | @fabricstack/orchestrator-sdk | dist/cli/mcpServeEntry.js | babysitter-mcp-server; the adapters/adapters-hooks re-export shims are dropped |
observer | @fabricstack/observer | dist/cli.js | babysitter-observer-dashboard |
harness | @fabricstack/harness-sdk | dist/bin/adapters.js | adapters |
| — | @fabricstack/harness-cli | delegates to @fabricstack/harness-sdk | — (none today) |
harness-mock | @fabricstack/harness-mock | dist/bin/adapters-harness-mock.js | adapters-harness-mock, mock-harness |
harness-tasks | @fabricstack/harness-tasks | dist/cli/index.js | adapters-tasks, tasks-adapter |
harness-triggers | @fabricstack/harness-triggers | dist/cli.js | adapters-triggers, triggers-adapter |
harness-channels | @fabricstack/harness-channels | dist/cli.js | adapters-channels, mcp-channels |
harness-extensions | @fabricstack/harness-extensions | dist/cli.js | adapters-extensions, extensions-adapter |
model-gateway | @fabricstack/model-gateway | dist/bin/adapters-transport-proxy.js | adapters-transport-proxy, adapters-proxy |
harness-hooks | @fabricstack/harness-hooks-cli | dist/cli/main.js | adapters-hooks, a5c-hooks-adapter |
agent-runtime | @fabricstack/agent-runtime-cli | dist/cli/main.js | genty |
console-tui | @fabricstack/console-tui | dist/bin/adapters-tui.js | adapters-tui |
catalog | @fabricstack/catalog | dist/cli.js | atlas, a5c-atlas |
control-plane-server | @fabricstack/control-plane | bin/kradle-server.mjs | kradle-server (also resolved the collision with the private @fabricstack/control-plane-cli dev bin) |
control-plane-demo | @fabricstack/control-plane | bin/kradle-demo.mjs | kradle-demo |
operator | @fabricstack/operator | dist/cli.js | kradle-install |
Private (non-publishable) §3.2 workspaces keep their dev-only bins (kip, kip-mcp, kradle, kradle-server, kradle-jitsi-agent-*); they never reach a registry and are subject only to the duplicate-bin rule of G5.
Backward compatibility
None. The public a5c-ai/babysitter repository keeps publishing the old bins under @a5c-ai/* (D17); the private train never installs alongside them under the same names (spec 15 §4.3 G5 public-train-bin), so npm i -g of a public and a private package can never EEXIST on each other.
Historical plan (public train, before D17)
8 CLI binaries were to be aligned to an adapters-{feature} pattern with a deprecated alias printing [adapters] "<old>" is deprecated, use "<new>" instead. for one major cycle (adapters-proxy → adapters-transport-proxy, a5c-hooks-adapter → adapters-hooks, extensions-adapter → adapters-extensions, triggers-adapter → adapters-triggers, tasks-adapter → adapters-tasks, mock-harness → adapters-harness-mock; adapters and adapters-tui unchanged). That alias guidance predates the two-repo model and is retired.