What it does
The reply — and any artifact commissioned while the mode holds — in Wu Chinese. A mode: it stays until changed or cleared with lang:off.
The registry's own words: Answer in Wu Chinese: replies — and artifacts commissioned while this mode is active — are delivered in Wu Chinese until another `lang:` directive replaces it or `lang:off` clears it back to the conversation's own language. The name is two letters in full; it fires at its full name — the floor never exceeds the name.
Fire it — usage examples
“Explain the deposit rules.
lang:wu”→ the explanation arrives in Wu Chinese, and the mode is confirmed like any mode.
language:wu on— from here on, everything in Wu Chinese.→ every reply, and every artifact made meanwhile, in Wu Chinese, until
lang:off.
Said aloud: “Lingo, language Wu Chinese — the two quotes, compared.”
→ the comparison arrives in Wu Chinese; the name is spoken in the language you are already speaking, never in the target tongue.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “language Wu Chinese”. Dictated directives fire deliberately, never by accident.
What the agent actually does
The agent sets its output language to Wu Chinese for the reply and for any artifact commissioned while the mode holds, and records the mode like any mode state — written in the turn it is set, confirmed, read back at session start. Register within Wu Chinese remains style:'s work.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-lang-wu ↗.
When the host can't
No Wu Chinese on this host: say so plainly in the reply, answer in the conversation's language, and never fake fluency the host does not have or silently substitute a different language. Still record the preference when the user sets one, disclosing that it cannot be executed here.
Conformance — “done when”
The reply (and any artifact in it) is in Wu Chinese, or the host's gap is disclosed — fluency is never faked.
Persistence class: mode-state. Execution report in the reply: required. A user can test any of this by hand — fire the directive, then check the result against the store, the schedule, or the reply itself.