docs: Enhance Frostwall vs Firefrost naming clarification
Expanded brief naming doc into comprehensive guide: - Clear definitions of Firefrost (brand) vs Frostwall (security) - Etymology and conceptual alignment explained - Common mistakes with corrections - Quick reference decision tree - Implementation checklist - Communication guidelines - Examples of correct usage - Audit commands to find incorrect usage Ran audit: No incorrect usage found in current documentation. All instances of mixed terminology are in example/warning contexts. Task: Fix Frostwall vs Firefrost Naming (Tier 3) FFG-STD-002 compliant
This commit is contained in:
Claude
@@ -1,25 +1,149 @@
|
||||
# Fix Frostwall vs Firefrost Naming
|
||||
# Fix Frostwall vs Firefrost Naming - Clarification Guide
|
||||
|
||||
**Status:** Ready
|
||||
**Priority:** Tier 3 - Documentation
|
||||
**Time:** 15 minutes
|
||||
**Last Updated:** 2026-02-16
|
||||
**Time Estimate:** 15 minutes
|
||||
**Last Updated:** 2026-02-17
|
||||
|
||||
## Problem
|
||||
Inconsistent terminology: "Frostwall" (network security) vs "Firefrost" (brand). Clarify usage in all docs.
|
||||
---
|
||||
|
||||
## Solution
|
||||
- **Frostwall:** Network security protocol (GRE tunnels, DDoS protection)
|
||||
- **Firefrost:** Company/brand name
|
||||
## The Problem
|
||||
|
||||
## Tasks
|
||||
1. Audit all docs for naming confusion
|
||||
2. Update incorrect usages
|
||||
3. Document terminology in standards
|
||||
4. Add to style guide
|
||||
Throughout the documentation and communications, "Frostwall" and "Firefrost" are sometimes used interchangeably or incorrectly. This creates confusion about whether we're talking about:
|
||||
- The security protocol
|
||||
- The company brand
|
||||
- A specific feature
|
||||
|
||||
## Success Criteria
|
||||
- ✅ Naming clarified throughout docs
|
||||
- ✅ Style guide updated
|
||||
**We need consistent terminology that everyone understands.**
|
||||
|
||||
**Fire + Frost + Foundation** 💙🔥❄️
|
||||
---
|
||||
|
||||
## Official Terminology
|
||||
|
||||
### FIREFROST (The Brand)
|
||||
|
||||
**What it is:** The company, the network, the community
|
||||
|
||||
**Official name:** Firefrost Gaming
|
||||
|
||||
**Usage:**
|
||||
- "Welcome to Firefrost Gaming"
|
||||
- "Firefrost subscriber network"
|
||||
- "The Firefrost community"
|
||||
- "Firefrost modpack servers"
|
||||
- "Fire + Frost philosophy"
|
||||
|
||||
**When to use:**
|
||||
- Company/brand references
|
||||
- Marketing materials
|
||||
- Player-facing communications
|
||||
- Social media
|
||||
- Domain names (firefrostgaming.com)
|
||||
|
||||
**Examples:**
|
||||
- ✅ "Firefrost Gaming is launching in Spring 2026"
|
||||
- ✅ "Join the Firefrost community"
|
||||
- ✅ "Firefrost subscriber perks"
|
||||
- ❌ "The Frostwall Gaming network" (incorrect)
|
||||
|
||||
---
|
||||
|
||||
### FROSTWALL (The Security Protocol)
|
||||
|
||||
**What it is:** The GRE tunnel security architecture
|
||||
|
||||
**Official name:** The Frostwall Protocol
|
||||
|
||||
**Usage:**
|
||||
- "The Frostwall Protocol protects our servers"
|
||||
- "Frostwall GRE tunnels"
|
||||
- "Frostwall deployment"
|
||||
- "Iron Wall security via Frostwall"
|
||||
|
||||
**When to use:**
|
||||
- Technical documentation
|
||||
- Infrastructure discussions
|
||||
- Security architecture
|
||||
- Internal operations
|
||||
- Server configuration
|
||||
|
||||
**Examples:**
|
||||
- ✅ "The Frostwall Protocol uses GRE tunnels for DDoS protection"
|
||||
- ✅ "Frostwall deployment blocks Mailcow installation"
|
||||
- ✅ "Testing Frostwall tunnel connectivity"
|
||||
- ❌ "Firefrost tunnels" (incorrect - too vague)
|
||||
- ❌ "The Frostwall gaming network" (incorrect - that's Firefrost)
|
||||
|
||||
---
|
||||
|
||||
## Why "Frostwall"?
|
||||
|
||||
**Etymology:**
|
||||
- **Frost:** From "Firefrost" - represents technical precision, protection, "cold" defense
|
||||
- **Wall:** Iron Wall security philosophy - impenetrable boundaries
|
||||
|
||||
**Conceptual alignment:**
|
||||
- Firefrost = Fire (warm, community) + Frost (cool, technical)
|
||||
- Frostwall = The "Frost" side protecting the infrastructure
|
||||
- Like a fortress wall made of ice - beautiful but impenetrable
|
||||
|
||||
**Not called "Firewall":**
|
||||
- Too generic (firewall is a standard networking term)
|
||||
- Doesn't align with "Frost" technical precision theme
|
||||
- Could be confused with UFW (Uncomplicated Firewall)
|
||||
|
||||
---
|
||||
|
||||
## Quick Reference
|
||||
|
||||
**Am I talking about the company/brand/community?**
|
||||
→ Use **Firefrost Gaming** or **Firefrost**
|
||||
|
||||
**Am I talking about the security architecture?**
|
||||
→ Use **The Frostwall Protocol** or **Frostwall**
|
||||
|
||||
**Am I talking about both?**
|
||||
→ "Firefrost Gaming's infrastructure is protected by the Frostwall Protocol"
|
||||
|
||||
---
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
**Wrong:** "Welcome to Frostwall Gaming!"
|
||||
**Right:** "Welcome to Firefrost Gaming!"
|
||||
|
||||
**Wrong:** "Configure the Firefrost tunnels"
|
||||
**Right:** "Configure the Frostwall tunnels"
|
||||
|
||||
**Wrong:** "Deploy the Firefrost Protocol"
|
||||
**Right:** "Deploy the Frostwall Protocol"
|
||||
|
||||
---
|
||||
|
||||
## Implementation Checklist
|
||||
|
||||
### Phase 1: Audit (5 min)
|
||||
|
||||
```bash
|
||||
cd /home/claude/firefrost-operations-manual
|
||||
grep -r "Frostwall Gaming" docs/
|
||||
grep -r "Firefrost Protocol" docs/
|
||||
grep -r "Firefrost tunnel" docs/
|
||||
```
|
||||
|
||||
### Phase 2: Correct (5 min)
|
||||
|
||||
Update files with incorrect terminology
|
||||
|
||||
### Phase 3: Document (5 min)
|
||||
|
||||
Add to style guide and standards
|
||||
|
||||
---
|
||||
|
||||
**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
|
||||
|
||||
---
|
||||
|
||||
**Document Status:** COMPLETE
|
||||
**Ready for Implementation:** YES
|
||||
|
||||
Reference in New Issue
Block a user