Product naming for contributors
Model-visible agent context uses the WednesdayAI brand. Operator identifiers, disk paths, env vars, and SDK package names stay openclaw. This page is the contract for code and tests that touch either side.Case map (exact)
Do not invent other spellings (
Wednesday AI, wednesday-ai, Openclaw, …).
KEEP classes (never blind-rename)
Even when a string is model-visible or adjacent to REPLACE text, keep these byte-identical:OPENCLAW_*env vars~/.openclaw/,openclaw.json, service/unit names, sockets,/__openclaw__/canvas/- TypeScript identifiers (
OpenClawConfig,createOpenClawTools, …) - Import specifier
wednesdayai/plugin-sdk(legacyopenclaw/plugin-sdkspecifier still loads per ADR 2057), and dual package/bin aliases - Legacy package-pack manifest key
openclaw(canonicalwednesdayai; legacy key still loads per ADR 2057), legacy manifest filenameopenclaw.plugin.json(canonicalwednesdayai.plugin.json; legacy filename still loads per ADR 2057) __OPENCLAW_REDACTED__,openclaw.inbound_meta.v1,provider: "openclaw"- Tool-group name
group:openclaw, browserprofile="openclaw", Lobster stepopenclaw.invoke
profile="openclaw" next to “openclaw-managed browser” prose), change only the prose token.
Prompt markers (lockstep)
src/agents/system-prompt-report.ts must import those constants — never re-hardcode marker literals. Assembler and parser are same-binary pairs (ADR 0051).
Surfaces that must say WednesdayAI
- System prompt identity and section headings (
## WednesdayAI Self-Update,## WednesdayAI CLI Quick Reference, docs block, tool blurbs) - Subagent / announce / group intro strings that the model reads
- Tool error and status text reused into model context (including
session_statusversion line, browser relay icon name) - Bundled skill descriptions/bodies and workspace templates under
docs/reference/templates/ - Model-taught docs base URL:
https://docs.wednesdayai.dev - Model-taught CLI spelling: primary binary
wednesdayai(openclawremains a legacy alias at the process boundary, under staged removal per ADR 2057)
Public import surface
Plugins and extensions import from the canonical SDK specifier:src/.
Guard tests
Update colocated string assertions in the same change as the source rename. Prefer at least one test that builds the real prompt (or real tool result) rather than only checking a helper return value.
What not to do
Related
- Admin/operator guide: Product naming
- User summary: What is WednesdayAI?
- System Prompt, Prompt Caching
- ADR 0051:
dev-docs/adr/0051-system-prompt-markers-wednesdayai.md