e23b6a7e69
The logged-in panel is now Catalyst Console (by Corrosion); the marketing site
keeps Corrosion as the platform/company and introduces the lexicon.
- Wordmark: panel/auth Logo lockup -> 'Catalyst' / 'by Corrosion'; the shared
C-core house mark (CorrosionMark) is untouched. Marketing nav/footer keep the
'Corrosion' wordmark.
- Titles: panel routes -> '{View} · Catalyst'; auth -> Catalyst; document.title
fallback + index.html -> 'Catalyst Console'. Marketing titles stay '— Corrosion'.
- Host agent user-facing copy -> 're-Agent' across panel + marketing (the
binary filename / CDN URLs / config paths / domains are UNCHANGED — that's the
separate infra/binary-rename sprint; 'Download re-Agent' fetching
corrosion-host-agent-* is the intended intermediate state).
- Deploy-recipe 'blueprint/template' -> 'Formula/Formulae' in marketing + roadmap;
Rust in-game 'blueprint wipe' kept (game term).
- docs/BRANDING.md added (Oracle review + locked lexicon).
vue-tsc + vite green; rendered clean both faces (Catalyst panel / Corrosion
marketing), 0 console errors.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
4.4 KiB
Corrosion — Brand & Naming Taxonomy
Source: Oracle (brand review), 2026-06-12.
Status: Reference / proposal.
Locked (2026-06-12): Catalyst Console (control panel/UI — chosen over "Catalyst Control Panel") · Substrate (bare-metal execution / process-automation plane) · re-Agent (host node agent, binary corrosion-re-agent-<platform>), under the Corrosion Management house. The "brought to you by Corrosion Management and Chemistry" line is flavor copy, not canonical.
Leaning (not yet final): Formula/Formulae for deploy manifests (replacing "Blueprints"), repo = Formulary, CLI catalyst deploy --formula rust.
Reserved well (adopt per-feature as built, don't name vaporware): the extended terms below — Formulae, Reaction Jobs, Compounds, Lab Notes, Substrate Engine, etc. — are Oracle's proposed expansion.
That rebrand is way stronger than "Corrosion Management Panel."
You now have a real naming system instead of a generic panel name:
Corrosion Management
├─ Catalyst Control Panel
├─ Substrate
└─ re-Agent
That works because all three names belong to the same metaphor family:
| Name | Meaning | Product fit |
|---|---|---|
| Corrosion | transformation, decay, reaction, harsh environments | game/server management brand |
| Catalyst | accelerates reactions without being consumed | operator/admin control panel |
| Substrate | material/process layer where reaction happens | automation/workflow engine |
| re-Agent | chemical reagent + remote agent pun | host/node agent |
Catalyst Control Panel is especially good. It sounds polished, memorable, and domain-specific without being cartoonish. It also gives you a clean product phrase:
"Manage your servers from Catalyst."
or
"Catalyst by Corrosion."
Tightened brand hierarchy
Corrosion
Game server orchestration platform
Catalyst
The web control panel
Substrate
The automation and process engine
re-Agent
The BYOH node agent
Chemistry
Optional umbrella/library/ecosystem name
Tagline caution
The one thing to be careful with is the phrase:
"brought to you by Corrosion Management and Chemistry"
That is clever, but maybe a little wordy for production branding. Use it as flavor copy, not the canonical name.
Better canonical versions:
Catalyst Control Panel
by Corrosion
Catalyst
A Corrosion Management product
Catalyst
Powered by Corrosion Chemistry
Binary naming
The binary naming is solid:
corrosion-re-agent-win-amd64.exe
corrosion-re-agent-linux-amd64
corrosion-re-agent-linux-arm64
corrosion-re-agent-darwin-arm64
Use linux instead of nix in binary names unless you specifically mean all Unix-like systems — nix-amd64 can be confused with NixOS / the Nix package manager. For clarity:
corrosion-re-agent-linux-amd64
corrosion-re-agent-windows-amd64.exe
Favorite full taxonomy
Corrosion
├─ Catalyst Console # UI/control panel
├─ Substrate Engine # automation/workflows
├─ re-Agent # BYOH host/node agent
├─ Formulae # server templates/manifests
├─ Reaction Jobs # queued automation runs
├─ Compounds # grouped services/stacks
└─ Lab Notes # audit/log/event history
That gives Corrosion its own identity while still letting OxideDock sit underneath as the container orchestration substrate.
Clean separation
Catalyst / Corrosion
Game-aware:
- Dune BattleGroups
- Rust servers
- wipes
- mods
- game lifecycle
- player/admin-facing concepts
OxideDock
Infra-aware:
- Docker
- Compose
- Swarm
- agents
- logs
- metrics
- stack deploys
- audit
So in practice:
Catalyst asks:
"Deploy Dune BattleGroup Alpha."
Substrate decides:
"Run the BattleGroup deployment workflow."
re-Agent reports:
"This BYOH node is ready."
OxideDock executes:
"Render/deploy/update the container stack."
That is a very clean product ecosystem.
One rename suggestion
Consider Catalyst Console over Catalyst Control Panel for the polished SaaS/product name. But if you like the old-school "control panel" vibe, Catalyst Control Panel absolutely works.