Vocabulary
Every Foxora product uses the same vocabulary. Use these terms in docs, output, and onboarding to keep the narrative coherent.
Glossary
| Generic term | Foxora term | Where it appears |
|---|---|---|
| package | kit | "Installed 3 kits" |
| AI agent | vixen | "vixen suggests…" |
| notification | howl | (rare in shell output, common on Foxora OS) |
| search | scent | fur scent postgres (alias for fur search) |
| workspace | territory | tabs on Foxora OS |
Names
- Product — Foxora Shell.
- Binary —
foxsh(short, memorable, greppable). Afoxorasymlink ships for discoverability. - Command plane —
fur(always lowercase, always a word, never an acronym). - Class of product — "terminal" (not "shell" to end users — the technical distinction is confusing).
Commands stay literal
Functional English in the command surface (fur install, fur search) so they're discoverable and Googleable. Use Foxora vocabulary in output prose ("Installed 3 kits"), never force it in command names.
Banned phrases (in user-facing chrome)
- "Powered by Ratatui" — only in About / docs credits.
- "Built on Nix" — hidden from user output.
- "Our fork of…" — rebrand cleanly, don't surface fork history.
- Negative framing against competitors in copy.
One narrative
The single line every Foxora Shell surface should reinforce: "one command plane for your system lifecycle."